>It's ugly, but there is a workaround for this now in respecifying the
>URLs in the child POMs. It's a pain but it's not the end of the world
>and I'd say better than adding even more voodoo.
Most people would say this isn't an acceptable workaround.
>I would say that's the best way to go - keep
>behaving the same way as now for 4.0.0 POMs, and come up with a better
>solution for people that choose to use 4.1.0 POMs (once they are in
>place).
I'm leaning this way but I was hoping we could find some solution. It is
a popular issue and I'd hate to just punt it. Anyone else have a
suggestion?
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...