Yes, but the tooling point only applies partially - there is no tooling for the various plugin configurations including the new configuration for this plugin. So there is no tooling support for that regardless which way we go.
I agree for inheritance and profiles...however I think we could go without them for the most use cases. In any way I'll try to talk to some Maven guys during the ApacheCon. Regards Carsten 2011/11/5 Jukka Zitting <[email protected]>: > Hi, > > On Sat, Nov 5, 2011 at 3:03 AM, Carsten Ziegeler <[email protected]> wrote: >> [...] just read the pom file ourselves to parse the annotations [...] > > What about POM inheritance and profiles? Or stuff like polyglot POMs? > > Sticking with standard Maven dependencies and the normal plugin > configuration mechanism is IMHO a much more failsafe and future-proof > approach. It also works well with IDEs and other tools that understand > Maven. > > BR, > > Jukka Zitting > -- Carsten Ziegeler [email protected]
