I find it strange that software would react differently simply because someone upgraded the POM version. It should act differently if a different setting is specified.
My recommendation is: 1) Solve it the correct way. Change the plugin/component to generate the paths in the fashion intended. Allow a configuration setting to revert behavior. 2) In the superpom, default to the new plugin/component version. 3) If corporations want the old behavior, they can override it in their corporate pom. Paul On Fri, Mar 7, 2008 at 3:30 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > >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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
