Question regarding Java versions (and POMs) about aldica

[AFaust]

The module inherits Java 8 as required version from the Acosix Maven parent POM for 6.0.7 ga. The module is already Java 11 compatible (as far as Alfresco is "compatible"), and only requires some additional JVM parameters to be set to suppress / avoid specific errors. I realise now these parameters are missing from the Readme, and currently only found in the Repository POM as part of the Docker-based integration test (see bottom of that file for the profile to test Alfresco 6.1). Andreas Kring <[email protected]> schrieb am Mo., 29. Apr. 2019, 16:22:

…

According to the Alfresco documentation the supported versions of Java is both Java 8 and Java 11 for Alfresco 6.0.1 and Java 11 for Alfresco 6.1. Which versions of Java is required/used to build the module? As I understand it, this should be handled via the POM(s) and the toolchain, but I am not sure where this info is available in the POM(s)? The reason I ask is that I build the module on my local machine (which has Java 8 available but not Java 11) and then deploy it in a LXC having only Java 11 available. When I started Tomcat there were errors from the module in the log, but then I installed Java 8 in the LXC and then everything worked fine. Is it necessary to tweek some Java settings (in the POM(s) or elsewhere) to get the module working with Java 11? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAQ35QJJ7J3PFFGOT5J5SPTPS4ADFANCNFSM4HJDYMOQ> .

[andreaskring]

Ok - thanks. So to fix the problem when running Java 11, all I have to do is to add these to my JAVA_OPTS?:

--add-exports=java.base/jdk.internal.misc=ALL-UNNAMED
--add-exports=java.base/sun.nio.ch=ALL-UNNAMED
--add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED
--add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
--add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED
--illegal-access=permit

If this is the case, I can add this info to the readme.

[AFaust]

That's correct. The last parameter (permit illegal access) is actually the Java default, I just wanted to make sure. Andreas Kring <[email protected]> schrieb am Di., 30. Apr. 2019, 09:39:

…

Ok - thanks. So to fix the problem when running Java 11, all I have to do is to add these to my JAVA_OPTS?: --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED --illegal-access=permit If this is the case, I can add this info to the readme. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAQ35QNQHKEV4AVCGX6K7XTPS7ZS5ANCNFSM4HJDYMOQ> .

[andreaskring]

Ok - I'll add the info to the readme

[andreaskring]

I have tested the extra flags needed for Java 11 and everything worked fine. Information about these flags have been added to the readme. Closing this issue.