• Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • core
    • Java 17 Phase 1: Support Java 17

      Add support for Java 17 in preview form while continuing to support and recommend Java 11.

      The most common issue is mixing mocks with JenkinsRule-based integration tests, resolved by either reducing the use of mocks (thereby turning the test into a pure integration test) as was done in JENKINS-68025, or increasing the use of mocks (thereby turning the test into a pure unit test) as was done in JENKINS-69353.

          [JENKINS-67908] Java 17 Phase 1: Support Java 17

          Andre Crespo added a comment - - edited

          How can I run jenkins 2.357 on systemd? I just change the JAVA_HOME environment variable from /opt/jdk11 to /opt/jdk17 but the service failed.

          I am using Adoptium Semeru distribution (Open J9) on both versions (11 and 17)

          Andre Crespo added a comment - - edited How can I run jenkins 2.357 on systemd? I just change the JAVA_HOME environment variable from /opt/jdk11 to /opt/jdk17 but the service failed. I am using Adoptium Semeru distribution (Open J9) on both versions (11 and 17)

          Basil Crow added a comment -

          acrespo This is not a support site; please use the users mailing list or community forum for this kind of question.

          Basil Crow added a comment - acrespo This is not a support site; please use the users mailing list or community forum for this kind of question.

          Basil Crow added a comment -

          Here are the types that I have observed to be problematic with XStream on Java 17:

          • java.util.concurrent.ConcurrentLinkedDeque
          • java.util.concurrent.ConcurrentLinkedQueue
          • java.util.concurrent.ConcurrentSkipListMap
          • java.util.concurrent.CountDownLatch
          • java.util.concurrent.CountDownLatch$Sync
          • java.util.concurrent.atomic.AtomicBoolean (tracked in https://github.com/x-stream/xstream/issues/308)
          • java.util.logging.Level
          • java.util.logging.LogRecord

          Basil Crow added a comment - Here are the types that I have observed to be problematic with XStream on Java 17: java.util.concurrent.ConcurrentLinkedDeque java.util.concurrent.ConcurrentLinkedQueue java.util.concurrent.ConcurrentSkipListMap java.util.concurrent.CountDownLatch java.util.concurrent.CountDownLatch$Sync java.util.concurrent.atomic.AtomicBoolean (tracked in https://github.com/x-stream/xstream/issues/308 ) java.util.logging.Level java.util.logging.LogRecord

            Unassigned Unassigned
            basil Basil Crow
            Votes:
            4 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: