Details
-
Task
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
None
-
2
-
Orion
-
Orion.Cycle1.Sprint3, Orion.Cycle2.Sprint1, Orion.Cycle2.Sprint2, Orion.Cycle2.Sprint3
-
Undetermined
Description
In the current Jakarta branch, there's a bit of dependency hell regarding activation jars.
project/pom.xml contains
- jakarta.activation:jakarta.activation-api:runtime:2.1.2 (${jakarta-activation.version})
- com.sun.activation:jakarta.activation:runtime:2.0.1 (${activation.version} )
- javax.activation:activation:compile:1.1.1 (${javax.activation.version})
- org.apache.sling:org.apache.sling.javax.activation:test:0.1.0${sling-javax-activation.version}
Also com.sun.mail:jakarta.mail:jar pulls in com.sun.activation:jakarta.activation:jar
AFAIK, activation jars are provided in the Tomcat container so should not end up in the cms.war (nor site.war). In the archetype, there's a jakarta.activation:jakarta.activation-api:runtime in the cargo.run and dist profiles which confirms that.
#1 see below
#2 unknown what to do there, remove possibly?
#3 javax, to be removed
#4 should probably not be present, depends on rest-assured
In other modules there are jakarta.activation-api mixed provided and compile dependencies which should be looked at what is best. This is because jakarta.activation.DataHandler is needed at compile time from org.apache.cxf.jaxrs.ext.multipart.Attachment#getDataHandler
- community/site-toolkit/components/jaxrs
- enterprise/replication/replication-source
- enterprise/replication/replication-target
- enterprise/synchronization/synchronization-source
- enterprise/targeting/rest-service