[
https://issues.apache.org/jira/browse/MNG-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MNG-4537.
-------------------------------------
Resolution: Auto Closed
Fix Version/s: (was: Issues to be reviewed for 3.x)
> --update-snapshots command line option flag is misleading, as it actually
> updates releases too
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-4537
> URL: https://issues.apache.org/jira/browse/MNG-4537
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
> Affects Versions: 2.0.9, 2.0.10, 2.2.1, 3.0-alpha-5, 3.0-alpha-6
> Reporter: Matthew McCullough
> Priority: Major
> Attachments: remove-misleading-updatesnapshots-option.patch
>
>
> Had a discussion with Brett Porter, Brian Fox, and Benjamin Bentmann on IRC
> about how the --update-snapshots command line option is misleading. I, as
> well as some of my students, we using -up, expecting downloads that
> previously failed to be tried again. However, that flag only checks for
> metadata updates to see if a newer version of the plugin has been released.
> What we were after is the -U flag (synonymous with --update-snapshots) which
> also checks again remotely for SNAPSHOT and RELEASE downloads that previously
> failed.
> Brett and Brian suggested that we either deprecate the old --update-snapshots
> long option, but that's not entirely possible since the short and long
> options are tied together. So, as a compromise solution, I'm indicating that
> the --update-snapshots option flag (name) may go away in the future and
> adding a migrate-to option called --update-all which was suggested in the
> above IRC conversation. Functionally, this long flag performs the same
> operation as --update-snapshots, but the name much more effectively
> communicates that it updates all artifacts from remote repos, not just
> snapshots.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
