[
https://issues.apache.org/jira/browse/CXF-7899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686049#comment-16686049
]
Hans Brende commented on CXF-7899:
----------------------------------
Yuck yuck yuck yuck yuck. Ok, so javax.activation-api needs to be excluded from
*everything*, because it *itself* has an *undeclared direct compile-time
dependency* on classes in com.sun.activation! So using javax.activation-api in
*any capacity whatsoever* is inherently prone to disaster.
Why anyone would design an api module in this manner is beyond me.
But at least we know what the fix is!
> Java 11 and javax.activation dependencies
> -----------------------------------------
>
> Key: CXF-7899
> URL: https://issues.apache.org/jira/browse/CXF-7899
> Project: CXF
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Freeman Fang
> Priority: Major
>
> Again, many apologies if this is a duplicate. Over on TIKA-2778, we're
> trying to add only the minimal dependencies that will allow us to compile and
> run with Java 11.
> We tried adding
> {noformat}
> <!-- for java 10 -->
> <dependency>
> <groupId>org.glassfish.jaxb</groupId>
> <artifactId>jaxb-runtime</artifactId>
> <version>2.3.1</version>
> </dependency>
> {noformat}
> However, as [~HansBrende] pointed out, this includes some of the
> javax.activation classes, but not those in com.sun.activation.*
> Any chance you'd be willing to migrate away from classes in this namespace?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
