A
I think this is *critical* to reduce build fragility which is
currently affects many/most Maven 2 builds.
IMO, making the version required, just like it is for dependencies is
a bit of a burden, but will dramatically increase the build longevity
of Maven 2 projects.
(And actually, once the pom include/merge|plugin-pack thingy is
sorted out, then the burden is going to drop off dramatically, since
the Maven team can publish a plugin-pack pom with each Maven release
with the know/tested/recommended versions of plugins, and the Mojo
folks can do the same).
--jason
On Sep 1, 2007, at 7:48 PM, Brett Porter wrote:
I'd like to hear from as many people as possible their opinion this
topic (even if you just want to say '0' so we know where you stand).
[ ] (A) All plugin versions must be specified by the project or its
parent hierarchy somewhere, at the cost of some verbosity (though
we should look at ways to make this easier/smaller/etc per the
current discussion)
[ ] (B) Retain the current behaviour, but make using the enforcer a
best practice to do the above, or some other control mechanism such
as having the repository manager handle the available plugins
[ ] (C) No opinion
[ ] (D) Undecided
[ ] (E) Other (please specify)
Thanks,
Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
