[MAGNOLIA-5981] Keep third party libraries in sync with the latest version used in main Created: 11/Nov/14  Updated: 30/Mar/15  Resolved: 19/Feb/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Epic Priority: Neutral
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
relation
is related to MAGNOLIA-6013 Upgrading versions of third-party lib... Closed
Template:
Epic Name: Keep 3rd-party libraries in sync
Acceptance criteria:
Empty
Date of First Response:

 Description   

Each cell should take care of updating the third-party libs in their modules so that they match the gav (groupId:artifactId:version) used in the foundational projects, i.e main and ui. This is necessary to avoid ending up with bundles containing conflicting versions of the same 3rd-party libs, especially when groupId and/or artifactId have changed, in which case Maven won't handle this and won't pick up the latest version automatically.



 Comments   
Comment by Magnolia International [ 11/Nov/14 ]

If we keep on using scope:import in bundles, there shouldn't be conflicts. What needs to be closely monitored is what changed in each dependency, and how it affects each and every module.

when groupId and/or artifactId have changed, in which case Maven won't handle this and pick up the latest version automatically.

It won't, it'll use both, since there's no way for Maven to know they're the same thing (unless the projects have setup relocations, which most don't)

Comment by Federico Grilli [ 11/Nov/14 ]

Yes, badly phrased - I meant Maven won't pick up the latest version automatically Thanks for the hint about scope:import anyway.

Generated at Mon Feb 12 04:10:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.