[ https://issues.apache.org/jira/browse/CXF-7899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686518#comment-16686518 ]
Tim Allison commented on CXF-7899: ---------------------------------- Y, the JDK11 profile is the right way to go. Over on Tika, for now, I think we'll go with the knuckle-dragging option of including with exclusions. :D In hindsight, this is definitely _not_ CXF's fault...sorry...but it is something to be aware of. It might be useful to add a unit test...if you don't have one...along the lines of: {{AttachmentUtil.getCommandMap();}} which triggers {{CommandMap.getDefaultCommandMap();}}, which currently requires the com.sun.* mess. Thank you, [~ffang] and [~HansBrende]! > 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)