But this is how it already works, if I'm reading correctly. The
minimum version of Maven for a plugin is specified by the plugin
itself in the prerequisites tag - if you use an older version of
Maven, you will get the last version of the plugin that worked with it.
- Brett
On 13/02/2008, at 8:22 AM, Paul Benedict wrote:
I've been watching the discussions about introducing a fix set of
plugin
versions per Maven version. I see benefit and drawback to each side
of the
argument.
Here is another proposal which is dear to my pain :-)
Provide the minimal compatible version of each plugin (of group
org.apache.maven.plugins) in the super pom. For instance, when I
upgraded to
Maven 2.0.8, it would have been nice (stupendous!) to automatically be
bumped to surefire 2.4 because the two truly needed each other in
integration testing. I imagine there are other cases when plugins have
dependencies on other parts of the Maven core, but I could be wrong.
The
desire is for children pom to provide the "better" versions if
necessary,
but Maven should at least provide the minimum versions.
Paul
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
