Skip to main content
V
VC_93914771-Visitor
1-Visitor
September 7, 2020
Solved

Eclipse JDK8 to JDK11 Issue: Package is accessible from more than one module

  • September 7, 2020
  • 3 replies
  • 115024 views

When trying to compile the Windchill Customizations (developed originally using JDK 8/Windchill 11) using JDK 11 (Windchill 12) we are getting compilation issues due to several packages being accessible from multiple modules.

 

For ex: org.w3c.dom package is now included in jdk11 jar by default (Module Path), but is also present in ie3rdpartylibs, xmlParserAPIs and dom4j jars (Class path).

 

We understand that JDK 11 is enforcing a modularity check to ensure the same package is not referenced in multiple jars. However it is also understood that module-info.java is not necessary to be configured for JDK 8 to 11 migration. As long as the relevant jars are added to the classpath, the code should be able to compile using JDK 11 as well.

 

How does PTC handle these issues when working with JDK 11 and Eclipse (version 4.16)?

 

VC_9391477_0-1599513136249.png

 

    Best answer by DC_8714414

    Thanks for the reply.  Very informative.

    The problem that I'm facing isn't that a package exists in multiple JARs.  The conflict that I'm running into is where a package in one of the JARs is also included in the JDK distribution.  For instance org.w3c.dom is in the WEB-INF/lib/ie3rdpartylibs.jar and is also provided in jdk11 (Corretto).  I wasn't aware that there was a way to resolve this without removing that package from ie3rdpartylibs.jar.  There are other packages in ie3rdpartylibs.jar that we need, so I need to leave that on my classpath.

     

    Dan

    3 replies

    A
    aacciano314-Alexandrite
    14-Alexandrite
    September 21, 2020

    I am really interested about this issues.

    @VC_9391477 

    Have you found a solution?

    @wsaad , maybe you can help us or point out to the correct reference?

    D
    DC_87144147-Bedrock
    7-Bedrock
    September 28, 2020

    It seem there are really only 2 options here ...

    1. Set compiler compliance to 1.8.  This results in a warning that the compiler (11) and compliance (1.8) are mismatched.
    2. Repackage PTC provided JAR files to remove the duplication.

    I not a fan of hiding problems, but I'm going with option 1 for now and hoping PTC will clean up the JAR files in a future release.

    A
    23-Emerald I
    avillanueva23-Emerald I
    23-Emerald I
    September 13, 2022

    Another option:

    I experienced similar issue when updating from java 8 to java 11. Steps below helped me,

    • Right click Eclipse project > Properties > Java Build Path
    • In Libraries tab, remove all the external jar files under Modulepath and add them under Classpath (you can just select all the jars and drag them under Classpath)
    • Click Apply and Close

    Note: JRE System Library will remain under Modulepath.

      D
      DKWc15-Moonstone
      15-Moonstone
      June 5, 2023

      Thanks.
      It solved for me.

      T
      TiemoVorschuetz8-Gravel
      8-Gravel
      September 29, 2020

      Hi,
      the srcLib folder is intend to deliver all dependencies used to build Windchill including their transitive dependencies.

      The ie3rdPartylib and the wc3rdPartyLib are sub sets built using either infoenginejars.xml or windchill3rdPartyJars.xml ant script located inside the srclib folder. Those ant scripts are intend to merge some single jars coming from the srclib into one uber-jar and strip of duplicates.

      Thus, you should remove your duplicates from the classpath to get rid of your conflicts. Also, you could use one of the common dependency management solutions like gradle or maven to manage your jars. PTC does not deliver their codebase and transitive dependencies by such a dependency management solution outside PTC itself. Therefore, you have to install maven (nexus or jfrog artifactory) or gradle on your local infrastructure and deploy all your necessary dependencies on your own.

      If a dependency is missing, deploy it from out of the srclib to maven/gradle server and extend your class path or maven dependencies for your project.

      Best regards,
      Tiemo Vorschuetz - INNEO Solutions

      D
      DC_87144147-BedrockAnswer
      7-Bedrock
      September 29, 2020

      Thanks for the reply.  Very informative.

      The problem that I'm facing isn't that a package exists in multiple JARs.  The conflict that I'm running into is where a package in one of the JARs is also included in the JDK distribution.  For instance org.w3c.dom is in the WEB-INF/lib/ie3rdpartylibs.jar and is also provided in jdk11 (Corretto).  I wasn't aware that there was a way to resolve this without removing that package from ie3rdpartylibs.jar.  There are other packages in ie3rdpartylibs.jar that we need, so I need to leave that on my classpath.

       

      Dan

        A
        aacciano314-Alexandrite
        14-Alexandrite
        September 29, 2020

        Dan,

         

        I recall reading somewhere that JDK Corretto is not supported on the client side and you will still have to use the oracle one.

        I am not sure if this is your use case though.

         

        Antonio

        Terms & ConditionsCookie settingsAccessibility statement