-
Bug
-
Resolution: Fixed
-
Blocker
-
None
-
Jenkins 2.303.1, OpenJDK 11
-
-
3.0.5
Xunit still seems to rely on the built-in JAXB-API, which has been removed on Java 11. Version 11 on the other hand is recommended by the current LTS version of Jenkins.
Other plugins (like cppcheck) solved this by using the JAXB plugin of Jenkins.
Typical error message:
Test Suite 'Dummy' passed at 2021-08-27 17:05:28.329.FATAL: Implementation of JAXB-API has not been found on module path or classpath.
[JENKINS-66475] Dependency on JAXB-API preventing migration to Java 11
Maximilian
created issue -
Maximilian
made changes -
| Description |
Original:
Xunit still seems to rely on the built-in JAXB-API, which has been removed on Java 11. Version 11 on the other side is recommended by the current LTS version of Jenkins.
Other plugins solved this by using the JAXB plugin of Jenkins. Typical error message: Test Suite 'Dummy' passed at 2021-08-27 17:05:28.329.FATAL: Implementation of JAXB-API has not been found on module path or classpath. |
New:
Xunit still seems to rely on the built-in JAXB-API, which has been removed on Java 11. Version 11 on the other hand is recommended by the current LTS version of Jenkins.
Other plugins solved this by using the JAXB plugin of Jenkins. Typical error message: Test Suite 'Dummy' passed at 2021-08-27 17:05:28.329.FATAL: Implementation of JAXB-API has not been found on module path or classpath. |
Maximilian
made changes -
| Description |
Original:
Xunit still seems to rely on the built-in JAXB-API, which has been removed on Java 11. Version 11 on the other hand is recommended by the current LTS version of Jenkins.
Other plugins solved this by using the JAXB plugin of Jenkins. Typical error message: Test Suite 'Dummy' passed at 2021-08-27 17:05:28.329.FATAL: Implementation of JAXB-API has not been found on module path or classpath. |
New:
Xunit still seems to rely on the built-in JAXB-API, which has been removed on Java 11. Version 11 on the other hand is recommended by the current LTS version of Jenkins.
Other plugins (like [cppcheck|https://plugins.jenkins.io/cppcheck/]) solved this by using the JAXB plugin of Jenkins. Typical error message: Test Suite 'Dummy' passed at 2021-08-27 17:05:28.329.FATAL: Implementation of JAXB-API has not been found on module path or classpath. |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Fixed but Unreleased [ 10203 ] |
| Released As | New: 3.0.3 | |
| Status | Original: Fixed but Unreleased [ 10203 ] | New: Resolved [ 5 ] |
Actually, the issue still exists in 3.0.4. We are unable to migrate to Java 11.
Jenkins 2.303.3, Ubuntu 20.04, OpenJDK11
"Test Suite 'Dummy' passed at 2021-11-09 12:45:51.579.FATAL: Implementation of JAXB-API has not been found on module path or classpath."
Maximilian
added a comment - - edited Actually, the issue still exists in 3.0.4. We are unable to migrate to Java 11.
Jenkins 2.303.3, Ubuntu 20.04, OpenJDK11
"Test Suite 'Dummy' passed at 2021-11-09 12:45:51.579.FATAL: Implementation of JAXB-API has not been found on module path or classpath." 
Kalle Niemitalo
added a comment - The dependency in pom.xml has <version>jaxb-2.3.0.1</version>. Should that be <version>2.3.0.1</version> instead, like in https://plugins.jenkins.io/jaxb/#dependencies?
Kalle Niemitalo
added a comment - The dependency in pom.xml has <version>jaxb-2.3.0.1</version> . Should that be <version>2.3.0.1</version> instead, like in https://plugins.jenkins.io/jaxb/#dependencies ? Kalle Niemitalo
added a comment - Also, the jaxb reference in pom.xml is within the dependencyManagement element. Doesn't that mean it only overrides the version of an existing dependency and does not add a new dependency?
Kalle Niemitalo
added a comment - Also, the jaxb reference in pom.xml is within the dependencyManagement element. Doesn't that mean it only overrides the version of an existing dependency and does not add a new dependency?
Any update on when this will actually be released?