Brett Porter wrote:
I think it's more complicated than just removing that.
Firstly, large numbers of command line plugins will stop working.
Secondly, we need to provide a solution for implied plugins (we can set
the version in the lifecycle and then let the user give pluginManagement
to override it, but I'd like to see plugin 'packs' as a better solution
to reduce the amount of configuration needed).
Thirdly, we need to think carefully about the impact on existing builds.
We're not just impacting the people that wrote the build - we impact the
random people that grab a project and unwittingly try and build it with
2.1 not knowing the author never tested that, and get the bad experience.
I'm still in favour of a compatibility mode that can be driven by the
prerequisites or the modelVersion. I say let people use the dependency
plugin now to start fixing their builds, but for 2.1 let them make the
conscious decision to move up to this.
I've talked about this before and I still mean that Maven should have a
prerequisite flag for Maven version as you're saying.
--
Trygve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
