[
http://jira.codehaus.org/browse/MVERSIONS-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=240100#action_240100
]
Stephen Connolly commented on MVERSIONS-130:
--------------------------------------------
might need to merge in some of the update-properties stuff too but again
limited to the reactor... of course if we are being pedantic we could just
override the property specified versions with the reactor version...
the use case for this is CI integration builds checking multiple modules
against each other, where those modules in SCM only depend on released versions
of the other modules, but we want the CI build to check the -SNAPSHOTs against
each other
> use-reactor mojo
> ----------------
>
> Key: MVERSIONS-130
> URL: http://jira.codehaus.org/browse/MVERSIONS-130
> Project: Maven 2.x Versions Plugin
> Issue Type: New Feature
> Affects Versions: Backlog
> Reporter: Stephen Connolly
> Priority: Minor
>
> This goal would be somewhat similar to the use-latest goals except it would
> only update dependencies that are within the reactor to the reactor version.
--
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
