Java 8 is reaching end of life. Newer versions of Oracle JDK will be paid. For long term support we should start using OpenJDK both for runtime and compilation.
Some changes done required for LAMS to run on OpenJDK 11:
1. javax.activation package is not a part of JDK anymore. We use a version delivered with WildFly.
2. Xerces had to be upgraded for Tool Deployer. In the future, Xalan will be the main Java tool to work with XML. It had to be used for lams_saml already.
3. HTTP connection implementations had to manually exposed for compilation as java.base module does not export them by default.
Marcin Cieslak
added a comment - Some changes done required for LAMS to run on OpenJDK 11:
1. javax.activation package is not a part of JDK anymore. We use a version delivered with WildFly.
2. Xerces had to be upgraded for Tool Deployer. In the future, Xalan will be the main Java tool to work with XML. It had to be used for lams_saml already.
3. HTTP connection implementations had to manually exposed for compilation as java.base module does not export them by default.
1. javax.activation package is not a part of JDK anymore. We use a version delivered with WildFly.
2. Xerces had to be upgraded for Tool Deployer. In the future, Xalan will be the main Java tool to work with XML. It had to be used for lams_saml already.
3. HTTP connection implementations had to manually exposed for compilation as java.base module does not export them by default.