[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687207#comment-16687207 ] Hudson commented on TIKA-2778: -- SUCCESS: Integrated in Jenkins build tika-branch-1x #128 (See [https://builds.apache.org/job/tika-branch-1x/128/]) TIKA-2778 -- Upgrade jaxb-runtime and javax.activation for use in Java > (tallison: [https://github.com/apache/tika/commit/f9eec836e285c95770b23c9ce685ce5275e74e84]) * (edit) CHANGES.txt * (edit) tika-langdetect/pom.xml * (edit) tika-server/src/test/java/org/apache/tika/server/TikaResourceTest.java * (edit) NOTICE.txt * (edit) tika-server/pom.xml * (edit) tika-parent/pom.xml * (edit) tika-parsers/pom.xml > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Assignee: Tim Allison >Priority: Major > Fix For: 2.0.0, 1.20 > > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686875#comment-16686875 ] Hudson commented on TIKA-2778: -- SUCCESS: Integrated in Jenkins build Tika-trunk #1594 (See [https://builds.apache.org/job/Tika-trunk/1594/]) TIKA-2778 -- Upgrade jaxb-runtime and javax.activation for use in Java > (tallison: [https://github.com/apache/tika/commit/0b3ef49f83f084079dcd611de54b1431d15e1078]) * (edit) tika-langdetect/pom.xml * (edit) tika-parsers/pom.xml * (edit) tika-server/src/test/java/org/apache/tika/server/TikaResourceTest.java * (edit) tika-parent/pom.xml * (edit) tika-server/pom.xml * (edit) CHANGES.txt * (edit) NOTICE.txt > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686834#comment-16686834 ] Hudson commented on TIKA-2778: -- UNSTABLE: Integrated in Jenkins build tika-2.x-windows #349 (See [https://builds.apache.org/job/tika-2.x-windows/349/]) TIKA-2778 -- Upgrade jaxb-runtime and javax.activation for use in Java > (tallison: rev 0b3ef49f83f084079dcd611de54b1431d15e1078) * (edit) CHANGES.txt * (edit) tika-langdetect/pom.xml * (edit) NOTICE.txt * (edit) tika-parent/pom.xml * (edit) tika-server/src/test/java/org/apache/tika/server/TikaResourceTest.java * (edit) tika-parsers/pom.xml * (edit) tika-server/pom.xml > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686068#comment-16686068 ] Hans Brende commented on TIKA-2778: --- [~ffang] No, that dependency is from org.glassfish.jaxb:jaxb-runtime:2.3.1 (which replaces jaxb-impl and jaxb-core, which are the "old" versions). Cf. https://issues.apache.org/jira/browse/TIKA-2743 > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[
https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686064#comment-16686064
]
Freeman Fang commented on TIKA-2778:
Guys, I don't think this dependency
{code}
javax.activation
javax.activation-api
{code}
is from CXF, CXF add this to a profile used by JDK11. But profile won't be
activated in your project if you have any CXF dependency, right? Unless your
project pom.xml has cxf parent.
> Upgrade jaxb-runtime and javax.activation
> -
>
> Key: TIKA-2778
> URL: https://issues.apache.org/jira/browse/TIKA-2778
> Project: Tika
> Issue Type: Task
> Components: parser
>Affects Versions: 1.19.1
>Reporter: Hans Brende
>Priority: Major
>
> The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a
> few issues on Java 11. A few important notes to take into consideration:
> 1. jaxb-core is no longer a separate artifact, but has been merged into
> jaxb-runtime.
> 2. jaxb-runtime now pulls in the latest version of the activation API, which
> is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact
> does not include a couple of the source files found in
> javax.activation:activation:1.1.1 (namely, those found in the
> com.sun.activation.* packages). The activation artifact which includes those
> extra sources has moved to: com.sun.activation:javax.activation:1.2.0.
> *However*, if I'm seeing this correctly, the com.sun.activation artifact
> *duplicates* all the code found in the activation-api artifact, rather than
> depending on it. If that's the case, and *if* you still need those extra
> classes in the activation artifact, one might need to manually exclude the
> activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain
> here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686061#comment-16686061 ] Hans Brende commented on TIKA-2778: --- [~talli...@apache.org] +1, I think manually excluding javax.activation-api everywhere it occurs is the only way to go here. Since javax.activation-api itself has a compile-time dependency on the classes in com.sun.activation, using it in any capacity, as far as I can see, is prone to disaster. I have no freaking clue why anyone would design an api module in this manner. > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[
https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686036#comment-16686036
]
Tim Allison commented on TIKA-2778:
---
This works...but...yuck!
{noformat}
${project.groupId}
tika-parsers
${project.version}
javax.activation
javax.activation-api
${project.groupId}
tika-langdetect
${project.version}
javax.activation
javax.activation-api
com.sun.activation
javax.activation
1.2.0
{noformat}
> Upgrade jaxb-runtime and javax.activation
> -
>
> Key: TIKA-2778
> URL: https://issues.apache.org/jira/browse/TIKA-2778
> Project: Tika
> Issue Type: Task
> Components: parser
>Affects Versions: 1.19.1
>Reporter: Hans Brende
>Priority: Major
>
> The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a
> few issues on Java 11. A few important notes to take into consideration:
> 1. jaxb-core is no longer a separate artifact, but has been merged into
> jaxb-runtime.
> 2. jaxb-runtime now pulls in the latest version of the activation API, which
> is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact
> does not include a couple of the source files found in
> javax.activation:activation:1.1.1 (namely, those found in the
> com.sun.activation.* packages). The activation artifact which includes those
> extra sources has moved to: com.sun.activation:javax.activation:1.2.0.
> *However*, if I'm seeing this correctly, the com.sun.activation artifact
> *duplicates* all the code found in the activation-api artifact, rather than
> depending on it. If that's the case, and *if* you still need those extra
> classes in the activation artifact, one might need to manually exclude the
> activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain
> here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[
https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686026#comment-16686026
]
Tim Allison commented on TIKA-2778:
---
Minimal triggering code:
{noformat}
@Test
public void testBasicAttachmentMap() throws Exception {
try {
AttachmentUtil.getCommandMap();
} catch (Throwable t) {
t.printStackTrace();
}
}
{noformat}
Stacktrace:
{noformat}
INFO Setting the server's publish address to be http://localhost:9998/
INFO Logging initialized @5042ms to org.eclipse.jetty.util.log.Slf4jLog
INFO jetty-9.4.12.v20180830; built: 2018-08-30T13:59:14.071Z; git:
27208684755d94a92186989f695db2d7b21ebc51; jvm 11+28
INFO Started ServerConnector@2e029d61{HTTP/1.1,[http/1.1]}{localhost:9998}
INFO Started @5540ms
WARN Empty contextPath
INFO Started o.e.j.s.h.ContextHandler@42b64ab8{/,null,AVAILABLE}
java.lang.NoClassDefFoundError: com/sun/activation/registries/LogSupport
at javax.activation.MailcapCommandMap.(MailcapCommandMap.java:179)
at javax.activation.CommandMap.getDefaultCommandMap(CommandMap.java:85)
at
org.apache.cxf.attachment.AttachmentUtil.(AttachmentUtil.java:70)
at
org.apache.tika.server.TikaResourceTest.testBasicAttachmentMap(TikaResourceTest.java:200)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
at
com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Caused by: java.lang.ClassNotFoundException:
com.sun.activation.registries.LogSupport
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 28 more
INFO Stopped o.e.j.s.h.ContextHandler@42b64ab8{/,null,UNAVAILABLE}
{noformat}
> Upgrade jaxb-runtime and javax.activation
> -
>
> Key: TIKA-2778
> URL: https://issues.apache.org/jira/browse/TIKA-2778
> Project: Tika
> Issue Type: Task
> Components: parser
>Affects Versions: 1.19.1
>Reporter: Hans Brende
>Priority: Major
>
> The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a
> few issues on Java 11. A few important notes to take into consideration:
> 1. jaxb-core is no longer a separate artifact, but has been merged into
> jaxb-runtime.
> 2. jaxb-runtime now pulls in the latest version of the activation API, which
> is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact
> does not include a couple of the source files found in
> javax.activation:activation:1.1.1 (namely, those found in the
> com.sun.activation.* packages). The activation artifact which includes those
> extra sources has moved to: com.sun.activat
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685996#comment-16685996 ] Hans Brende commented on TIKA-2778: --- [~talli...@apache.org] would you mind posting the full stack trace you got? I'm trying to figure out what's actually going on here. > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685969#comment-16685969 ] Hans Brende commented on TIKA-2778: --- [~talli...@apache.org] Well, that's a bummer. I'm not 100% sure here, but your best bet in that case might be to *include* com.sun.activation:javax.activation:1.2.0 as an additional dependency and *exclude* javax.activation:javax.activation-api:1.2.0 from jaxb-runtime. > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[
https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685944#comment-16685944
]
Tim Allison commented on TIKA-2778:
---
Doh! tika-server needs it...
{noformat}
...
at
org.apache.cxf.jaxrs.client.WebClient.doChainedInvocation(WebClient.java:1050)
at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:897)
at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:866)
at org.apache.cxf.jaxrs.client.WebClient.invoke(WebClient.java:334)
at org.apache.cxf.jaxrs.client.WebClient.post(WebClient.java:343)
at
org.apache.tika.server.TikaResourceTest.testExtractTextAcceptPlainText(TikaResourceTest.java:330)
...
Caused by: java.lang.ClassNotFoundException:
com.sun.activation.registries.LogSupport
{noformat}
> Upgrade jaxb-runtime and javax.activation
> -
>
> Key: TIKA-2778
> URL: https://issues.apache.org/jira/browse/TIKA-2778
> Project: Tika
> Issue Type: Task
> Components: parser
>Affects Versions: 1.19.1
>Reporter: Hans Brende
>Priority: Major
>
> The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a
> few issues on Java 11. A few important notes to take into consideration:
> 1. jaxb-core is no longer a separate artifact, but has been merged into
> jaxb-runtime.
> 2. jaxb-runtime now pulls in the latest version of the activation API, which
> is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact
> does not include a couple of the source files found in
> javax.activation:activation:1.1.1 (namely, those found in the
> com.sun.activation.* packages). The activation artifact which includes those
> extra sources has moved to: com.sun.activation:javax.activation:1.2.0.
> *However*, if I'm seeing this correctly, the com.sun.activation artifact
> *duplicates* all the code found in the activation-api artifact, rather than
> depending on it. If that's the case, and *if* you still need those extra
> classes in the activation artifact, one might need to manually exclude the
> activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain
> here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685865#comment-16685865 ] Hans Brende commented on TIKA-2778: --- Yay! deleting two dependencies from pom == successful day > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[
https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685857#comment-16685857
]
Tim Allison commented on TIKA-2778:
---
Right... I made the upgrade to 2.3.1 locally. I don't think we'll need any
{{com.sun.activation}}. I'm still waiting for a complete build, but this
_seems to work_:
org.glassfish.jaxb
jaxb-runtime
${jaxb.version}
> Upgrade jaxb-runtime and javax.activation
> -
>
> Key: TIKA-2778
> URL: https://issues.apache.org/jira/browse/TIKA-2778
> Project: Tika
> Issue Type: Task
> Components: parser
>Affects Versions: 1.19.1
>Reporter: Hans Brende
>Priority: Major
>
> The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a
> few issues on Java 11. A few important notes to take into consideration:
> 1. jaxb-core is no longer a separate artifact, but has been merged into
> jaxb-runtime.
> 2. jaxb-runtime now pulls in the latest version of the activation API, which
> is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact
> does not include a couple of the source files found in
> javax.activation:activation:1.1.1 (namely, those found in the
> com.sun.activation.* packages). The activation artifact which includes those
> extra sources has moved to: com.sun.activation:javax.activation:1.2.0.
> *However*, if I'm seeing this correctly, the com.sun.activation artifact
> *duplicates* all the code found in the activation-api artifact, rather than
> depending on it. If that's the case, and *if* you still need those extra
> classes in the activation artifact, one might need to manually exclude the
> activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain
> here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685854#comment-16685854 ] Hans Brende commented on TIKA-2778: --- [~talli...@apache.org] Did upgrading to jaxb-runtime 2.3.1 do the trick, or are you still getting that error? > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685764#comment-16685764 ] Hans Brende commented on TIKA-2778: --- [~talli...@apache.org] Sorry, commented before seeing your comment. The 'javax.activation.DataSource' class should be pulled in by jaxb-runtime v. *2.3.1* (currently you have *2.3.0.1*). > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685763#comment-16685763 ] Hans Brende commented on TIKA-2778: --- [~talli...@apache.org] no worries! As regards this issue, do you have any idea if the com.sun.activation.* packages are used anywhere in Tika + dependencies, or will the new activation-api (without the com.sun.activation.* packages) suffice? > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685761#comment-16685761 ] Tim Allison commented on TIKA-2778: --- It looks like we do need the javax.activation dependency for compiling with Java 11. When I try to build with Java 11 without it, I get this: /...tika-parsers/src/main/java/org/apache/tika/parser/journal/GrobidRESTParser.java:[75,26] cannot access javax.activation.DataSource [ERROR] class file for javax.activation.DataSource not found org.apache.cxf.jaxrs.ext.multipart.Attachment uses: import javax.activation.DataHandler; import javax.activation.DataSource; > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685757#comment-16685757 ] Tim Allison commented on TIKA-2778: --- Sorry for the wrong commit message above. Those were for TIKA-2780. > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685691#comment-16685691 ] Hudson commented on TIKA-2778: -- SUCCESS: Integrated in Jenkins build tika-branch-1x #126 (See [https://builds.apache.org/job/tika-branch-1x/126/]) TIKA-2778 -- the shutdown method for tika-batch mode should not be (tallison: [https://github.com/apache/tika/commit/230997465a6eaed18d5309c3d32dd9af6182dd02]) * (edit) tika-batch/src/main/java/org/apache/tika/batch/InterrupterFutureResult.java * (edit) tika-batch/src/main/java/org/apache/tika/batch/BatchProcess.java * (edit) tika-batch/src/main/java/org/apache/tika/batch/Interrupter.java * (edit) tika-batch/src/main/java/org/apache/tika/batch/builders/InterrupterBuilder.java * (edit) tika-batch/src/main/java/org/apache/tika/batch/builders/BatchProcessBuilder.java * (edit) CHANGES.txt * (edit) tika-batch/src/main/java/org/apache/tika/batch/BatchProcessDriverCLI.java > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685677#comment-16685677 ] Hudson commented on TIKA-2778: -- SUCCESS: Integrated in Jenkins build Tika-trunk #1592 (See [https://builds.apache.org/job/Tika-trunk/1592/]) TIKA-2778 -- the shutdown method for tika-batch mode should not be (tallison: [https://github.com/apache/tika/commit/30c3d8104a51f015416382995435a4785059f07c]) * (edit) tika-batch/src/main/java/org/apache/tika/batch/BatchProcess.java * (edit) tika-batch/src/main/java/org/apache/tika/batch/Interrupter.java * (edit) tika-batch/src/main/java/org/apache/tika/batch/builders/BatchProcessBuilder.java * (edit) tika-batch/src/main/java/org/apache/tika/batch/InterrupterFutureResult.java * (edit) tika-batch/src/main/java/org/apache/tika/batch/BatchProcessDriverCLI.java * (edit) CHANGES.txt * (edit) tika-batch/src/main/java/org/apache/tika/batch/builders/InterrupterBuilder.java > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TIKA-2778) Upgrade jaxb-runtime and javax.activation
[ https://issues.apache.org/jira/browse/TIKA-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685654#comment-16685654 ] Hudson commented on TIKA-2778: -- UNSTABLE: Integrated in Jenkins build tika-2.x-windows #346 (See [https://builds.apache.org/job/tika-2.x-windows/346/]) TIKA-2778 -- the shutdown method for tika-batch mode should not be (tallison: rev 30c3d8104a51f015416382995435a4785059f07c) * (edit) tika-batch/src/main/java/org/apache/tika/batch/BatchProcessDriverCLI.java * (edit) tika-batch/src/main/java/org/apache/tika/batch/BatchProcess.java * (edit) tika-batch/src/main/java/org/apache/tika/batch/builders/InterrupterBuilder.java * (edit) tika-batch/src/main/java/org/apache/tika/batch/Interrupter.java * (edit) CHANGES.txt * (edit) tika-batch/src/main/java/org/apache/tika/batch/builders/BatchProcessBuilder.java * (edit) tika-batch/src/main/java/org/apache/tika/batch/InterrupterFutureResult.java > Upgrade jaxb-runtime and javax.activation > - > > Key: TIKA-2778 > URL: https://issues.apache.org/jira/browse/TIKA-2778 > Project: Tika > Issue Type: Task > Components: parser >Affects Versions: 1.19.1 >Reporter: Hans Brende >Priority: Major > > The latest version of org.glassfish.jaxb:jaxb-runtime is 2.3.1, which fixes a > few issues on Java 11. A few important notes to take into consideration: > 1. jaxb-core is no longer a separate artifact, but has been merged into > jaxb-runtime. > 2. jaxb-runtime now pulls in the latest version of the activation API, which > is: javax.activation:javax.activation-api:1.2.0. *However*, this artifact > does not include a couple of the source files found in > javax.activation:activation:1.1.1 (namely, those found in the > com.sun.activation.* packages). The activation artifact which includes those > extra sources has moved to: com.sun.activation:javax.activation:1.2.0. > *However*, if I'm seeing this correctly, the com.sun.activation artifact > *duplicates* all the code found in the activation-api artifact, rather than > depending on it. If that's the case, and *if* you still need those extra > classes in the activation artifact, one might need to manually exclude the > activation-api artifact pulled in by jaxb-runtime. But, I'm not 100% certain > here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
