[
https://jira.codehaus.org/browse/MNG-5528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338096#comment-338096
]
Chris Erskine commented on MNG-5528:
------------------------------------
I agree that the current text is what is done but people read it that 'updated
releases' will replace V2.5 with an updated V2.5. They do not pickup that
maven does not replace an existing version. I have had this problem at a number
of sites that I have gone into where they think they can update the current
version and do a -U to update the local repository rather than creating a new
version number.
Maybe adding that it does not update current released versions.
> Help text confuses people
> -------------------------
>
> Key: MNG-5528
> URL: https://jira.codehaus.org/browse/MNG-5528
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Command Line
> Affects Versions: 3.1.0
> Environment: any
> Reporter: Chris Erskine
> Priority: Minor
>
> When the 'mvn --help' command is used, the output for -U states "Forces a
> check for updated releases and snapshots on remote repositories". This
> confuses a lot of users into thinking that this option will update released
> versions of artifacts.
> Could this be changed to something like "Forces a check for updated snapshots
> on remote repositories"
> This would solve a number of problems that I have seen at different sites
> where people think they can patch a finally released artifact and it is
> updated in the local repository with the -U option.
> Updating the help text would then roll into documentation where the text is
> copied into it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
