Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:2
-
Epic Link:
-
Sprint:Fall 4 2023 Oct 16, Fall 5
Description
Attachments
Activity
There is a runtime error with the removal of JideSoft ultimate in Java 8 which has to do with the new JideTable class. This issue will be addressed in IGBF-3486
Some of the above dependencies has deprecated since Java 9 which explains the missing requirement but another missing requirement error was jdk.internal.module which exists in Zulu Java 11. Importing the package to igb module seems to resolve the error for now. Now the only error that appears is missing requirement, javax.xml.bind.
Some errors pointed to missing dependencies in das module as well:
<dependency>
<groupId>jakarta.xml.bind</groupId>
<artifactId>jakarta.xml.bind-api</artifactId>
<version>4.0.1</version>
</dependency>
<dependency>
<groupId>org.glassfish.jaxb</groupId>
<artifactId>jaxb-runtime</artifactId>
<version>4.0.3</version>
</dependency>
<dependency>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
<version>2.3.1</version>
</dependency>
<dependency>
<groupId>jakarta.xml.bind</groupId>
<artifactId>jakarta.xml.bind-api</artifactId>
<version>4.0.1</version>
</dependency>
Runtime errors of indicating missing requirement javax.activation was resolved by adding the following dependency in igb module:
<dependency>
<groupId>com.sun.activation</groupId>
<artifactId>javax.activation</artifactId>
<version>1.2.0</version>
</dependency>
Which was followed by several other similar errors resolved by and the following :
<dependency>
<groupId>org.glassfish.jaxb</groupId>
<artifactId>jaxb-runtime</artifactId>
<version>4.0.3</version>
</dependency>
<dependency>
<groupId>org.glassfish.hk2</groupId>
<artifactId>osgi-resource-locator</artifactId>
<version>2.4.0</version>
</dependency>
<dependency>
<groupId>com.sun.xml.fastinfoset</groupId>
<artifactId>FastInfoset</artifactId>
<version>2.1.0</version>
</dependency>
As this is an investigate issue and each error is going to have its own ticket from now on like the one above, this ticket is moved to close