![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
2.1 |
|
Assignee:
|
Unassigned |
|
Created:
|
28/Oct/13 9:30 AM
|
|
Description:
|
I would be nice if the use-lastest-versions (and all the use-latest-* and use-next-*) mojo could also update properties that define the version to be updated.
This would of course require that the property be defined locally in the same pom. I believe the fix is in PomHelper.setDependencyVersion, when it determines if haveOldVersion - around line 602. I will do my best to submit a patch for this, but I would like some idea of how likely it would be to be accepted (as a feature - assuming the patch is good enough).
(An added bonus would be to update properties in the parent poms if it is a multi-module project and the plugin is run from the top. But that is a much bigger and more difficult change.)
I would be happy if this feature were enabled by a property that was by default false to preserve existing behaviour.
I suppose this could be resolved by MVERSIONS-191 and then just using both update-properties use-latestversions together.
|
|
Project:
|
Mojo's Versions Maven Plugin
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Ben Tatham
|
|
|
|
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
|
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
