[
http://jira.codehaus.org/browse/MNG-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119530
]
Nick Stolwijk commented on MNG-3358:
------------------------------------
This is exactly what the enforcer plugin can do. I don't think that Maven
itself should do it.
> Require explicit plugin versions
> --------------------------------
>
> Key: MNG-3358
> URL: http://jira.codehaus.org/browse/MNG-3358
> Project: Maven 2
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Reporter: Paul Gier
>
> Currently plugin versions are not required in the pom which causes maven to
> use the latest version of each plugin to be used when building a project.
> The problem with this system is that builds can break (without any change to
> the project itself) if a new version of a plugin is released. This can cause
> confusion among developers because the build appears to break for no reason.
> It also makes reproducing old builds to be more difficult because a newer
> version of a plugin could cause some aspect of the build to be different than
> when it was originally released.
> SUREFIRE-61 is one example of where this happened. When surefire 2.3.1 was
> released, it affected the testing of some builds because the classpath
> ordering changed.
> My suggestion for fixing this is to require a version for all plugins. This
> is already a best practice among many maven users, but it is not enforced by
> maven itself. For the default lifecycle plugins (compiler plugin, surefire
> plugin, etc.) maven should tie it's version to specific default versions of
> the plugins. These could then be overridden when necessary.
> This change probably belongs in 2.1 since it is too big a change for 2.0.9.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
