maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Gier (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MNG-3358) Require explicit plugin versions
Date Fri, 11 Jan 2008 22:00:57 GMT

     [ http://jira.codehaus.org/browse/MNG-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paul Gier closed MNG-3358.
--------------------------

    Resolution: Won't Fix

You're right, this feature of the enforcer fits my needs.  Closing this issue since this feature
is not needed once enforcer 1.0 is released.

> 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

        

Mime
View raw message