[ http://jira.codehaus.org/browse/MPLUGIN-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144632#action_144632 ]
Benjamin Bentmann commented on MPLUGIN-132: ------------------------------------------- Updated German bundle in [r684476|http://svn.apache.org/viewvc?view=rev&revision=684476], feel free to close Vincent. > Don't encourage users to use "mvn -up" to update plugins > -------------------------------------------------------- > > Key: MPLUGIN-132 > URL: http://jira.codehaus.org/browse/MPLUGIN-132 > Project: Maven 2.x Plugin Tools > Issue Type: Improvement > Components: Plugin Plugin > Affects Versions: 2.4.2 > Reporter: Benjamin Bentmann > Priority: Minor > Fix For: 2.4.3 > > > Originally reported by Wendy on IRC: > {noformat} > 5:42 PM wsmoak bentmann: where does > http://maven.apache.org/plugins/maven-war-plugin-2.1-alpha-2/plugin-info.html > come from? > 5:42 PM wsmoak it says to run 'mvn -up' which isn't going to work in 2.0.9+ > {noformat} > More precisely, the generated "Plugin Documentation" says > {noformat} > You could run 'mvn -up' to get the latest version of this plugin > {noformat} > This only works for RELEASE/LATEST versions, which is now considered bad > practice and has already been disabled for common plugins by locking them > down in the super POM. Hence, we should update the documentation and remove > this suggestion. The one and only way to get a particular plugin version is > to explicitly specify it in the POM. > As Vincent further pointed out, this needs also to be addressed in the > announcment mail template given in [Releasing A Maven > Project|http://maven.apache.org/developers/release/releasing.html]. -- 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