Tips on compiling MAC projects using mvn and JDK > 8

[alick888]

1. Need to set multi-release to the correct JDK version, e.g. when using JDK 11, your command should look like this: 

1. mvn clean install -Dmaven.test.skip=true -DskipTests -Djdeps.multiRelease=11

2. Need additional permission when using JDK 17 or above, export an environment variable as follows:

1. export MAVEN_OPTS="--add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.util.regex=ALL-UNNAMED --add-opens=java.base/java.lang.reflect=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.xml/javax.xml.namespace=ALL-UNNAMED"

[amirkhan-ak-sf]

This is really working! We tried it yesterday on 3 different user machines! Thanks @alick888!

@arpitg-1 @dipeshkumardutta-sfemu FYI.

[dipeshkumardutta-sfemu]

Also, why are we compiling on java 17? our mule core modules are not compatible to be compiled using java 17. they can only run on java 17 runtime.

[amirkhan-ak-sf]

@dipeshkumardutta-sfemu The point here is to allow the compilation for use cases where Java 8 / 11 can not be installed and used as per policy. It is a workaround that is working until we can officially compile the connectors in Java 17+.

[dipeshkumardutta-sfemu]

I do not understand the need of this workaround. I am not aware of which policy. But as of now all our connectors are compiled in JAVA 8 and running on 8, 11 and 17.
So I think the same is applicable for this also.

[dipeshkumardutta-sfemu]

Oho! understood now. For those developer who cannot install java 8 in their machine. Am I right @amirkhan-ak-sf ?

[amirkhan-ak-sf]

100% yes, thats the use case.