Your message dated Wed, 20 Dec 2017 12:19:59 +0000
with message-id <20171220121959.ga18...@blind.goeswhere.com>
and subject line Can't reproduce.
has caused the Debian Bug report #874630,
regarding FTBFS with Java 9: javax.activation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
874630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libaxiom-java
Version: 1.2.8
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

This package fails to build with default-jdk pointing to openjdk-9-jdk.
Please fix it, so that we can start the transition to Java 9.


The wiki has some common problems and their solutions, including this
javax.activation change. No solution, as of today, though!
https://wiki.debian.org/Java/Java9Pitfalls

Build log:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on 
project axiom-api: Execution default-test of goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: There was an 
error in the forked process
[ERROR] java.lang.NoClassDefFoundError: javax/activation/DataSource
[ERROR]         at java.base/java.lang.Class.getDeclaredMethods0(Native Method)
[ERROR]         at 
java.base/java.lang.Class.privateGetDeclaredMethods(Class.java:3139)
[ERROR]         at 
java.base/java.lang.Class.getMethodsRecursive(Class.java:3280)
[ERROR]         at java.base/java.lang.Class.getMethod0(Class.java:3266)
[ERROR]         at java.base/java.lang.Class.getMethod(Class.java:2063)
[ERROR]         at 
org.apache.maven.surefire.common.junit3.JUnit3Reflector.createInstanceFromSuiteMethod(JUnit3Reflector.java:153)
[ERROR]         at 
org.apache.maven.surefire.common.junit3.JUnit3Reflector.constructTestObject(JUnit3Reflector.java:124)
[ERROR]         at 
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:74)
[ERROR]         at 
org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:136)
[ERROR]         at 
org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:109)
[ERROR]         at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:291)
[ERROR]         at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
[ERROR]         at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
[ERROR] Caused by: java.lang.ClassNotFoundException: javax.activation.DataSource
[ERROR]         at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
[ERROR]         at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:185)
[ERROR]         at 
java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:496)
[ERROR]         ... 13 more
[ERROR] -> [Help 1]



Cheers,
Chris.

--- End Message ---
--- Begin Message ---
This has gone away on my builder (the one that found the problem in the
first place); I suspect the problem was caused by visibility, which as
been changed in openjdk changes.

https://rbuild.fau.xxx/2017-12-20/success/libaxiom-java.log

Chris.

--- End Message ---
__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to