Replies: 2 comments
This comment was marked as spam.
This comment was marked as spam.
-
Thank you for your response! It turns out my workflow is a bit more complex as I am doing a JDK matrix [8,11], so the environment variable will have to change based on which JDK is running. I don't know how to set the right environment variable based on the JDK that is running. You can view my project at https://github.com/leerho/datasketches-memory-2.2.1 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Question
Body
I'm running a Java 11/ maven environment using JPMS where I need to export a few JVM packages.
In this situation it is an error to specify "--release" to the java compiler.
Executing "mvn clean compile" in a GitHub action, for some mysterious reason, automatically sets the compiler
"--release" flag, which fails the CI/CD build.
My pom files DO NOT specify this flag, yet running maven in the GitHub action inserts it anyway.
My pom files do specify "maven.compiler.source = 11" and "maven.compiler.target = 11".
Outputting the effective pom when executing the GH action reveals that all 3 flags are present!
Running "mvn clean compile" locally works fine.
How can I force this github action to not set the compiler "--release" flag?
Beta Was this translation helpful? Give feedback.
All reactions