[ROO-3465] Roo overwrites manual changes to the pom.xml Created: 02/Dec/13  Updated: 22/Feb/16  Resolved: 21/Jul/15

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

Type: Bug Priority: Critical
Reporter: Eric B Assignee: Juan Carlos GarcĂ­a del Canto
Resolution: Complete Votes: 0
Labels: roo
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relate
relates to ROO-3478 Maven Dependency Management - Increas... Resolved

 Description   

Whenever I make changes to artifacts in my pom.xml that are different than those initially populated by Roo, any command executed in the Roo shell that relies on those artifacts will reset them to values that Roo likes, but which may be incompatible with my application.

For example, I have upgrade Spring-Data to v1.4.1.RELEASE. However, if I create a new repository via the Roo shell, Roo will overwrite my version to v1.2.0.RELEASE.

This is problematic, especially if/when my code relies on newer constructs not available in the older versions as referenced by Roo.

I have noticed this occurring with Spring-Data as well as javax.validation.validation-api, although I presume that it occurs with other libs as well.



 Comments   
Comment by Alan Stewart [ 13/Dec/13 ]

Changing to an improvement. Currently Roo manages dependencies based the three Maven coordinates (ie groupId, artifactId, and version) to be able to add and delete if, for example, a jpa provider or database is changed. Not ideal I know. Note that in each Roo release we usually update dependencies to their current versions where we can

Generated at Wed Oct 23 07:28:46 UTC 2019 using Jira 7.13.8#713008-sha1:1606a5c1e7006e1ab135aac81f7a9566b2dbc3a6.