Uploaded image for project: 'Policy Framework'
  1. Policy Framework
  2. POLICY-4665

R13: Java 17 and associated dependency upgrade

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Medium Medium
    • Montreal Release
    • None
    • None
    • None
    • R13: Java 17 and associated dependency upgrade
    • Policy 2023-07-19->2023-08-02, Policy 2023-08-02->2023-08-17
    • Done

      This epic covers the upgrade of the Policy Framework to Java 17, Spring 6, Springboot 3 and associated dependencies.

      This upgrade is required to remove security vulnerabilities, especially in Springboot.

      see
      https://wiki.onap.org/display/DW/Dependency+Upgrade+in+Policy+Framework

       

      The things to do are:

      1. Remove dependency to oparent. We should take all the things in the oparent pom into policy/parent.
      2. On policy/parent/integration, on a local checkout, remove the oparent overrides
      3. On policy/parent/integration, raise all dependencies onto their latest versions.

      On policy/parent.integration, replace all "javax.' imports with their "jakarta." equivalents

      1. On policy/parent/integration, change <java.version>11</java.version> to 17
      2. On https://github.com/onap/policy-docker/blob/master/policy-jdk/alpine/src/main/docker/Dockerfile line 51, change openjdk11 to openjdk17
      3. On https://github.com/onap/policy-docker/blob/master/policy-jre/alpine/src/main/docker/Dockerfile line 50, change openjdk11 to openjdk17
      4. Start building locally
        1. parent
        2. docker
        3. common
        4. models
        5. etc
      5. Update jenkins jobs
      6. Update CSITs etc.

      What changes will be needed on each repo:

      1. All "javax." imports change to "jakarta."
      2. Some minor java17 code changes.
      3. Compile each repo and fix as you go

      Note: xacml-pdp uses a dependency that uses "javax" XML jars so there is incompatibility between the imports in XACML. We will solve this when we come to it.

       

      Look for abandoned commits around December 2022 for most of the detail on this change. The change was not pushed at that time as it was too disruptive.

            Unassigned Unassigned
            liamfallon liamfallon
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: