[
https://jira.codehaus.org/browse/MVERSIONS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280075#comment-280075
]
Arnout Engelen commented on MVERSIONS-85:
-----------------------------------------
I think it would be a bad idea for use-latest-release to downgrade SNAPSHOT's:
as Kalecser mentioned above, you might have upgraded to the latest SNAPSHOT for
a reason, and the real fix would be to create a new release of the dependency,
not to downgrade the SNAPSHOT.
It would be really awesome to automatically downgrade the SNAPSHOT dependencies
that have no relevant changes since the last release. Determining this would
probably be quite site-specific though (e.g. checking in SVN for relevant
commits since tagging the release).
For now the safest solution IMHO would be to leave the SNAPSHOT's with no new
releases alone, and have the user decide between releasing a new version or
downgrading the version. It might be an option to prompt for this when in an
interactive terminal.
For the brave, a 'roll-back-snapshots' mojo or '-DallowSnapshotsDowngrade=true'
might be useful, but I wouldn't use it.
> Allow versions:use-latest-release to change "1.1-SNAPSHOT" to "1.0"
> -------------------------------------------------------------------
>
> Key: MVERSIONS-85
> URL: https://jira.codehaus.org/browse/MVERSIONS-85
> Project: Maven 2.x Versions Plugin
> Issue Type: Improvement
> Affects Versions: 1.1
> Reporter: Matthew McEachen
> Fix For: Backlog
>
>
> I've just started using the versions plugin -- very nice work, guys!
> In trying out several of the goals, I applied "use-latest-snapshots" for
> internal project dependencies, just on the off-chance that the project would
> have new builds, we'd pick up those changes automatically. So, for example,
> my pom.xml now depends on 1.1-SNAPSHOT for a "company-common" project.
> Come release time for my project, though, several of the projects won't have
> bothered to do a release, as there wasn't anything to release, so I want to
> revert to 1.0 for "company-common".
> The versions plugin in this use case leaves me high and dry -- the
> "versions:use-latest-release" won't "downgrade" the 1.1-SNAPSHOT version to
> 1.0, and the maven release plugin will puke due to my SNAPSHOT dependency.
> Can we add a configuration property to support "use latest release, even if
> that means an older version than the current version"?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
