[
http://jira.codehaus.org/browse/MVERSIONS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208751#action_208751
]
Stephen Connolly commented on MVERSIONS-92:
-------------------------------------------
I'd rather add this functionality to the set plugin...
e.g.
mvn version:set -DgroupId=... -DartifactId=... -DnewVersion=...
as that will be a more generic solution.
> Add new mojo to set dependencies to a specific version
> ------------------------------------------------------
>
> Key: MVERSIONS-92
> URL: http://jira.codehaus.org/browse/MVERSIONS-92
> Project: Maven 2.x Versions Plugin
> Issue Type: New Feature
> Affects Versions: 1.2
> Reporter: Michael Spaulding
> Attachments: use-specific-version.patch
>
>
> Sometimes you want to explicitly set the version number for a dependency for
> an artifact or family of artifacts across a multi-module project. I propose
> we add a new goal to do this:
> use-specific-version
> Parameters:
> newVersion: The new version number to use.
> The mojo will be derived from AbstractVersionsDependencyUpdaterMojo, so it
> will pickup the includes/excludes functionality for specifying which
> dependencies should be updated.
> I've included the code for the new mojo along with an integration test.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
