openJDK-docker VS Maven Wrapper

Install OpenJDK and Java Runtime Environment (JRE) 11

Reloading is nothing new under the sun for Lisp, I believe. For ML and adequate reload-ability, one might be hard pressed, but it's nothing new under the Sun (hint, hint). Maybe too on the nose, but one probably wants good inlining, and thus more "speculative" de/optimisation to preserve redefinition.

If they don't want Oracle's Java, why can't they use a subset of OpenJDK (licensing noob here)?

I think they use a circular queue of functions that is each executed for around 100 ms. I am guessing the system timer is used to generate an interrupt that pauses execution of the current function and starts executing the next function. Apple's Java code is probably closed source. I did find mention of an openjdk here: https://openjdk.java.net. I haven't looked at the source code yet.

https://openjdk.java.net

$ yum info java-1.8.0-openjdk Available Packages Name : java-1.8.0-openjdk Arch : x86_64 Epoch : 1 Version : 1.8.0.322.b06 Release : 1.el7_9 Size : 314 k Repo : updates/7/x86_64 Summary : OpenJDK 8 Runtime Environment URL : http://openjdk.java.net/ License : ASL 1.1 and ASL 2.0 and BSD and BSD with advertising and GPL+ and GPLv2 and GPLv2 with : exceptions and IJG and LGPLv2+ and MIT and MPLv2.0 and Public Domain and W3C and zlib Description : The OpenJDK 8 runtime environment.

For the rest: -+ PIP3 & Python scripts: export REQUESTS_CA_BUNDLE=/path/to/your/certificate.pem python script.py -+ JAVA =java -D'javax.net.ssl.trustStore'="/opt/site/cacerts.JKS" .....= https://serverfault.com/questions/636612/preserve-imported-ca-certificates-through-java-upgrades/636882 https://github.com/docker-library/openjdk/issues/327 -+ Windows server https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/valid-root-ca-certificates-untrusted certutil .. root fg.cer

Maven also has the maven wrapper: https://github.com/takari/maven-wrapper which accomplishes the same thing.

When creating a new Maven project, Micronaut also configures the Maven wrapper.

IDE's can be fiddly, and anyway I don't think it's good to depend on an IDE for building.

The project could have been set up instead with the "Maven wrapper"(1) which provides "mvn.cmd/sh" scripts at the top level of the project to fetch and run the proper Maven. So after cloning the project, all you have to do is set a proper JAVA_HOME and then do "./mvn clean package". The IDE's will then set themselves up properly if you import the project as a Maven project, and will sync with changes to the Maven pom.xml whenever it changes (Intellij does at least). That's really hard to beat.

(1) https://github.com/takari/maven-wrapper (Being integrated into Maven itself soon).

I got it from here: https://github.com/takari/maven-wrapper

> Now “obviously” the answer is that we should have pegged the version of gradle required to use the script

My first step with either gradle or maven is to install the wrapper generator, which has this effect. After adding the wrapper you invoke it via ./gradlew or ./mvnw in the project doirectory.

It’s not perfect - especially in terms of IDE support - but it’s crucial to at least keeping your CLI builds consistent across team members and in automation.

gradle wrapper: https://docs.gradle.org/current/userguide/gradle_wrapper.htm...

maven wrapper: https://github.com/takari/maven-wrapper