You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2008/08/09 21:32:27 UTC
[jira] Created: (MPLUGIN-132) Don't encourage users to use "mvn
-up" to update plugins
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
[jira] Updated: (MPLUGIN-132) Don't encourage users to use "mvn
-up" to update plugins
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPLUGIN-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MPLUGIN-132:
--------------------------------------
Fix Version/s: 2.4.3
> 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
[jira] Commented: (MPLUGIN-132) Don't encourage users to use "mvn
-up" to update plugins
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (MPLUGIN-132) Don't encourage users to use "mvn -up"
to update plugins
Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPLUGIN-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton closed MPLUGIN-132.
-----------------------------------
Assignee: Vincent Siveton
Resolution: Fixed
Thanks!
> 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
> Assignee: Vincent Siveton
> 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
[jira] Commented: (MPLUGIN-132) Don't encourage users to use "mvn
-up" to update plugins
Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPLUGIN-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144630#action_144630 ]
Vincent Siveton commented on MPLUGIN-132:
-----------------------------------------
Fixed in r684473. Could you update the German bundle?
> 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