Clojurians Log v2

trying REBL on my Windows box. So far so good. I didn't have opportunity to try it before. @seancorfield you can check if you want. I updated manifest to the newest Clojure installation (1.10.1.502).

@ales.najmann which jdk did you try with?

adoptopenjdk-lts-hotspot from java bucket

thanks. just got that working. haven't had much luck with the jdk8 line of things yet. may be there are some missing bits.

btw, do you use anything to switch among various jdks? apart from manually setting env vars, that is.

https://github.com/borkdude/deps.clj/releases/tag/v0.0.7

Not on Windows, there I just stick to 11 LTS. On Mac I swithc between versions using JAVA_HOME and changing symlinks from time to time when I really need something extra.

thanks!

I don't specifically plan to return back to 8. Company just upgraded to 11 at minimum. Graalvm is released for Java 11. And I no longer develop for Android. So no reasons.

nice unfortunately, to do building of things like babashka, i still have to use 8

I used the Azul OpenJDK 8 w/JFX bundle for REBL.

Now I'm on Adopt OpenJDK 11 so I just use the OpenJFX 11 dependencies.

yes, that works nicely

FWIW, I have a few legacy processes that require JDK 8 so I use JAVA_HOME on macOS to select 8 for those in their startup scripts locally and in Tomcat's bin/setenv.sh on the two servers that need that.

@seancorfield thanks for mentioning azul's offerring i will try that. for switching environments in *nix environments there seem to be a number of options (though i didn't like jenv or sdkman very much). i've been using graal's select_jdk.py with a tweak or two (this doesn't really work for windows' cmd.exe or ps afaict) tomcat's bin/setenv.sh doesn't handle use from cmd.exe or powershell does it?

ah may be there is a setenv.bat...

No idea. All our servers are Linux and my current primary dev env is macOS.

tnx

We only recently upgraded from Adopt OpenJDK 8 to Adopt OpenJDK 11 on QA/production -- so many libraries and server packages we used took a long time to be JDK 9+ compatible 😞

Now, only our legacy CFML apps require JDK 8 🙂

going from 8 to 11 seems to have been bumpy...is it related largely to the module-related changes?

ah, the zulu openjdk8 + fx seems to work on windows with rebl :thumbsup: thanks again for the tip.

8 to 9 was really the big jump (due to modules, yes, specifically the change around the core JDK). 9 onward has been relatively straightforward. Another set of changes for us -- again 8 to 9 -- was the overall of GC logging so the set of options we used to start the JVM (for years) caused the JVM to not start because they'd made several long-standing options illegal (and there was no legal set of overlapping options we could use on both 8 and 9 so it was a painful upgrade because we had to do a bunch of manual changes around a JVM restart).

We'd been testing against 11 on and off for about a year I think (but hadn't tested all the production JVM options -- that was my bad!) so we'd been slowly tracking toward compatibility.