Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-66475

Dependency on JAXB-API preventing migration to Java 11

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • xunit-plugin
    • 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 added a comment -

          Any update on when this will actually be released?

          Maximilian added a comment - Any update on when this will actually be released?

          Nikolas Falco added a comment -

          has been released in 3.0.3

          Nikolas Falco added a comment - has been released in 3.0.3

          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."

          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."

          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 ?

          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?

          Reopening because the xunit plugin still doesn't have a dependency on the jaxb plugin according to https://plugins.jenkins.io/xunit/#dependencies, either.

          Kalle Niemitalo added a comment - Reopening because the xunit plugin still doesn't have a dependency on the jaxb plugin according to https://plugins.jenkins.io/xunit/#dependencies , either.

          Maximilian added a comment - - edited

          3.0.5 did not fix the issue for me. Still the same error message:
          "Test Suite 'Dummy' passed at 2021-11-09 20:53:56.235.FATAL: Implementation of JAXB-API has not been found on module path or classpath."

          When I switch back to Java 8, everything works fine.

          Maximilian added a comment - - edited 3.0.5 did not fix the issue for me. Still the same error message: "Test Suite 'Dummy' passed at 2021-11-09 20:53:56.235.FATAL: Implementation of JAXB-API has not been found on module path or classpath." When I switch back to Java 8, everything works fine.

          Nikolas Falco added a comment -

          if works for ccpplugin than works also for xunit 3.0.5 because is the same solution and jaxb classes (and impl) is in the dependency classpath.

          Nikolas Falco added a comment - if works for ccpplugin than works also for xunit 3.0.5 because is the same solution and jaxb classes (and impl) is in the dependency classpath.

          Nikolas Falco added a comment -

          Furthermore in out production enviroment we use Jenkins 2.303.3 and we do not have that issue.
          Provide please a full stack trace and job configuration to understand where is the problem (if there or somewhere else)

          Nikolas Falco added a comment - Furthermore in out production enviroment we use Jenkins 2.303.3 and we do not have that issue. Provide please a full stack trace and job configuration to understand where is the problem (if there or somewhere else)

          Maximilian added a comment -

          Okay, the new error was caused by our Xcode plugin. I'll investigate it further, I guess this issue can be closed. Thanks for the update!

          Maximilian added a comment - Okay, the new error was caused by our Xcode plugin. I'll investigate it further, I guess this issue can be closed. Thanks for the update!

            nfalco Nikolas Falco
            vogtmh Maximilian
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: