!aRKdLCkUeIFjRPZuJT:nixos.org

NixOS JVM

109 Members
24 Servers

Load older messages


SenderMessageTime
25 Apr 2025
@emilazy:matrix.orgemilylatest OpenJDK 21 release is https://github.com/openjdk/jdk21u/tags15:49:48
@ami:the-apothecary.clubAmiwhere i checked (nix-channel --update && nixos-rebuild switch and search.nixos.org) it's on 21.0.5+1115:49:51
@ami:the-apothecary.clubAmi * where i checked (nix-channel --update && nixos-rebuild switch, a few hours ago and search.nixos.org) it's on 21.0.5+11 15:51:13
@emilazy:matrix.orgemily oh, you're right. I editorialized slightly, oops – I checked staging just to be sure. turns out we have an update in the pipeline 15:54:35
@emilazy:matrix.orgemily we just started -next, so hopefully in a week or two? 15:54:44
@emilazy:matrix.orgemily(…hope we remembered to backport it to stable)15:54:57
@ami:the-apothecary.clubAmiah nice16:11:03
26 Apr 2025
@programmer_jarvis:matrix.orgPROgrm_JARvis joined the room.13:03:40
28 Apr 2025
@charlotte:vanpetegem.mechvp left the room.14:28:04
1 May 2025
@rosariopulella:matrix.orgRosario Pulella changed their display name from Rosario Pulella to Rosuavio.20:08:00
8 May 2025
@98765abc:mozilla.org98765abc changed their profile picture.11:35:19
9 May 2025
@frederic:scs.ems.hostFrédéric Christ changed their display name from Frédéric Christ to Frédéric Christ (🧳 12.05. - 02.06.).10:20:38
16 May 2025
@fliegendewurst:matrix.orgFliegendeWurstAnyone against packaging Temurin 25 early access? https://github.com/NixOS/nixpkgs/pull/36859820:15:37
@emilazy:matrix.orgemilynot certain I see the suitability for Nixpkgs. it poses similar maintenance burden to our other JDK versions (security patches etc.) and is even less good to rely on20:26:13
@emilazy:matrix.orgemilythough of course a binary build is less of a burden than a source one20:26:19
17 May 2025
@terrorjack:matrix.orgterrorjack set a profile picture.08:53:54
21 May 2025
@msgilligan:matrix.orgmsgilliganI'm ready to begin experimenting with JDK 25 and a Temurin EA binary build would be helpful. Since JDK 25 will be LTS and will be final in September, getting packages migrated to JDK 25 earlier will help get more ported in time for the Nix 25.11 release. (Projects using Gradle have a tougher time since Gradle is usually the critical path to upgrading to a new JDK. I'm considering migrating one project to Maven mainly for this reason.) As others have mentioned, things like EA releases could also be provided in a repo other than Nixpkgs. 22:16:38
22 May 2025
@raboof:matrix.orgraboofI agree the ideal solution would be to allow getting 'unusual' JVMs (such as EA ones) though packages outside of nixpkgs. Sadly the nix packaging for a JVM seems nontrivial and currently not easily reusable outside of nixpkgs, which is how I ended up proposing https://github.com/NixOS/nixpkgs/pull/368598 for now.09:47:50
@raboof:matrix.orgraboof(I used to have something based on https://github.com/shyiko/jabba but that seems no longer active)09:51:09
@raboof:matrix.orgraboofmight be worth revisiting seeing if we could plug the output of https://github.com/NixOS/nixpkgs/pull/368598/files#diff-f8aad332f02513cf4d092cf685ff2e8f43a9c09787a7212a8021c223bd6dc9e7 into https://codeberg.org/raboof/nix-jabba actually... realistically I won't have time for that for the next few weeks but if someone wants to give it a shot go for it ;)09:53:07
@msgilligan:matrix.orgmsgilligan

Well, the ideal solution would be to have them in Nixpkgs and to have the necessary developers to maintain them.

I really wish I had more time and more Nix knowledge. My Nix knowledge is growing though unfortunately my available time isn't. But I think #368598 is important and am willing to help test it.

(I use SDKMAN! and it is very useful when you are testing with a wide variety of JDKs, gradles, mavens. etc. At some point it might be nice to be able to install SDKMAN! with Nix.)

Maybe the best thing to do is create a JDK-focused fork of Nixpkgs with an integration branch. This would allow us to do more testing and integration prior to submission (and acceptance) by Nixpkgs.

17:33:38
@msgilligan:matrix.orgmsgilliganNote that I've previously talked about the challenges I've faced using Nixpkgs for "cutting-edge" JDK development. In particular the way one non-LTS JDK (e.g. 23) will disappear and new one (e.g. 24) will replace it in the same commit makes things challenging. Having access to EAs of new JDKs solves my problem in a more proactive way, by allowing developers to get ahead of the change by testing with the new JDK version sooner. The JDK 25 release will likely end my critical dependence on non-LTS JDKs, so the sooner we get there the better. If I focus on 25, it will help me and Nixpkgs get there sooner.17:40:38
@msgilligan:matrix.orgmsgilligan

BTW, JDK 25 version 25-ea+23, has the long-awaited JEP 512: Compact Source Files and Instance Main Methods implemented, so hello.java in the following format is both a valid Java program and a runnable script:

///usr/bin/env java "$0" "$@" ; exit $? 
void main() {
    IO.println("Hello, World!");
}
17:44:15
@msgilligan:matrix.orgmsgilliganMy reason for being dependent on these recent JDKs is the Foreign Function and Memory API introduced in Java 22.17:51:30
@qbig:matrix.org@qbig:matrix.org joined the room.19:22:27
@qbig:matrix.org@qbig:matrix.org left the room.19:44:42
23 May 2025
@raboof:matrix.orgraboof whoa is that // a sort of alternative shebang? what's that called? TIL 08:00:34
@qyliss:fairydust.spaceAlyssa RossI think it's relying on being run by a shell08:04:08
@qyliss:fairydust.spaceAlyssa RossAnd then it's just an absolute path08:04:15
@qyliss:fairydust.spaceAlyssa Rossi.e. execve wouldn't work, but shells usually fall back to executing as a shell script and that would work.08:05:06

Show newer messages


Back to Room ListRoom Version: 6