[ROO-3478] Maven Dependency Management - Increase Flexibility Created: 19/Jan/14  Updated: 01/Sep/15  Resolved: 01/Sep/15

Status: Resolved
Project: Spring Roo
Component/s: @ CORE
Affects Version/s: 1.2.5.RELEASE
Fix Version/s: 2.0.0.M2

Type: Improvement Priority: Minor
Reporter: Jack Matthews Assignee: Juan Carlos García del Canto
Resolution: Complete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Dependency Management


Issue Links:
Relate
is related to ROO-3465 Roo overwrites manual changes to the ... Resolved

 Description   

We would like to use roo but were unable to because of the limitations regarding maven dependency management.

Roo will revert manual changes to the pom.xml file which makes it difficult for us to update our dependencies.

For the initial project setup this is fine, from then on we should be able to tell roo to stop using pom.xml and start using a new file pom.roo.xml. We can then manually update our own pom.xml from pom.roo.xml as necessary.

For example: Say there is an xml configuration file in the project root directory called roo-settings.xml.

 
<rooSettings>
    <managePom>false</managePom>
</rooSetting>

If we set managePom to false, roo will stop managing our pom.xml file and start managing pom.roo.xml. All updates made by roo will now show in pom.roo.xml and we have to manually copy changes to pom.xml.

roo-settings.xml could be used for other future roo settings also.

This is Similar to this issue: https://jira.springsource.org/browse/ROO-3465



 Comments   
Comment by Juan Carlos García del Canto [ 01/Sep/15 ]

Solved on ROO-3465

Spring Roo only checks groupId and artifactId dependency, but if dependency version changes, ignores it.

Generated at Mon Jul 15 23:17:56 UTC 2019 using JIRA 7.9.2#79002-sha1:3bb15b68ecd99a30eb364c4c1a393359bcad6278.