[MAGNOLIA-3536] Webapp contains two versions of jdom. Created: 29/Jan/11  Updated: 13/Dec/11  Resolved: 03/Feb/11

Status: Closed
Project: Magnolia
Component/s: build
Affects Version/s: 4.4.2
Fix Version/s: 4.4.3, 4.5

Type: Bug Priority: Neutral
Reporter: Jörg Schaible Assignee: Ondrej Chytil
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

The bundled webapp contains in WEB-INF/lib jdom-1.0.jar as well as jdom-1.1. Reson is that jdom switched groupId:
jdom:jdom:1.0
org.jdom:jdom:1.1
The magnolia build should use exclusions for those deps that depend themselves on the old version.



 Comments   
Comment by Tobias Mattsson [ 11/Apr/11 ]

We know declare a jdom:jdom:1.1 as a dependency, which gets changed due to its relocation into org.jdom:jdom:1.1. Transitive dependencies on jdom:jdom:1.0 results in duplicate jars. These have been excluded and are not present in the bundle any more.

A more stable approach would be to add jdom:jdom:BANNED to dependencyManagement and change the explicit dependency to org.jdom:jdom.

Generated at Mon Feb 12 03:47:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.