Replies: 1 comment
-
|
People didn't like it when I enforced Azul Zulu for JVM choices for the templates... I'm definitely on board on specifying a default vendor for Cleanroom. I say we open a poll here or discord... |
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
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Avoid JVMs that break Cleanroom.
Goals
Force Gradle to avoid JVM implementations that Cleanroom is known to not work with.
Non Goals
Adding more features to CleanroomGradle.
Motivation
I have Semeru on all of my computers and for some God-forsaken reason Gradle auto-selects it, making it annoying to build Cleanroom, despite JAVA_HOME being set to a completely different implementation.
That might just be a problem with my computer but if this gets universally solved nobody else who might have a similarly dilapidated dev environment will not complain about it.
Description
Why?
Cleanroom does not work on every JVM implementation.
Some people have multiple kinds of JVM 21.
Gradle might auto select one that does not boot up Cleanroom.
What?
Force Gradle to avoid problematic JVMs.
How?
There are two ways this can be achieved. One is to use the functionality of tha java plugin in Gradle. The other is to write a plugin that will select the most appropriate JVM although that's most likely overkill.
Dependencies
No response
References
Gradle Toolchains
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions