[
https://issues.apache.org/jira/browse/CXF-7899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686079#comment-16686079
]
Hans Brende commented on CXF-7899:
----------------------------------
[~ffang] I'm not too familiar with profiles, so I can't really speak to that.
Perhaps [~talli...@apache.org] would know more about that than I do. (Note,
however, that including the extra jaxb & activation jars in Java 8 as well as
11 hasn't caused us any problems, and seems to be a rather common approach.)
All I know is that if javax.activation:javax.activation-api:1.2.0 is used on
Java 11 instead of com.sun.activation:javax.activation:1.2.0, you'll get
NoClassDefFoundErrors.
Tika's solution is probably going to be to manually exclude
javax.activation:javax.activation-api from any dependencies pulling it in
(namely, org.glassfish.jaxb:jaxb-runtime:2.3.1), and add an explicit dependency
on com.sun.activation:javax.activation.
> 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)
