In reply to @msgilligan:matrix.org

If someone wants to work to make the JDK toolchain binary free, the place to start might be with Maven. It is currently:

    sourceProvenance = with lib.sourceTypes; [
      binaryBytecode
      binaryNativeCode
    ];

In reply to @pyrox:pyrox.dev
okay yeah, let's just not bother with dropping it since adding the option would trigger rebuilds fafaik

In reply to @pyrox:pyrox.dev
working on this now, we have to bootstrap from ant -> maven 3.3.9(last version that can be built with ant) -> hopefully just the latest maven version

https://github.com/NixOS/nixpkgs/pull/484741 rebuild-linux:1001-2500 🫠

yeah I was kinda floored by that too. :) But since temurin bootstraps OpenJDK, basically anything that uses Java is affected.

I took a look at a couple (gnome-shell and python-vlc) and both have plausible-seeming explanations (gnome-shell depends on libphonenumber, which apparently uses Java for some of its test cases; python-vlc depends on libbluray, and Java is part of the BluRay platform as I recall from some excited JavaOne announcement a couple decades ago :) ).

I could not find a plausible explanation for a third package I looked at, pylatex. But, I don't think there's a way around a mass-rebuild here.

It looks like the jextract build has been broken on Darwin for almost a year. Here's a fix:

• https://github.com/NixOS/nixpkgs/pull/519643

In this comment on a PR to update maven, Benedikt Ritter (britter) says:

a ton of seemingly unrelated packages are being rebuilt, because igraph (a C library for analysis of networks) depends on Apache FOP (an XML formatter) which is built with maven. igraph only requires FOP for building it's documentation but this dependency still has rippling effects, e.g. the python packages now have a transitive dependency to maven because of that.

I've been doing some investigation and think I have a fix.

It turns out that igraph is simply copying its DocBook source to it's doc output and is not running either the html or pdf CMake targets that render the documentation. So I want to make a PR to do the following:

1. Actually enable the rendering of the HTML documentation.
2. Remove the dependency on FOP.

This should stop a lot of rebuilds (especially in Python packages) based on fop <- maven <- jdk.

It is two commits, and I have verified that the first one (removing fop) works independently, so it could be made into a separate PR if there is some objection to how the HTML docs are being generated, etc.

The removal of fop should make the pending Maven update less breaking and might be worth expediting.

The igraph update should reduce the number of package-build failures from 109 to about 40. And most (possibly even all) of the remaining failures are due to packages not having Stable Maven plugins as described in the Nixpkgs Manual:

Maven defines default versions for its core plugins, e.g. maven-compiler-plugin. If your project does not override these versions, an upgrade of Maven will change the version of the used plugins, and therefore the derivation and hash.

When maven is upgraded, mvnHash for the derivation must be updated as well: otherwise, the project will be built on the derivation of old plugins, and fail because the requested plugins are missing.

So to get an up-to-date Maven without breaking ~40 dependencies, for each dependency we need to either:

• Add a pom.xml patch, like this merged fix for fop: https://github.com/NixOS/nixpkgs/pull/522916
• Update the mavnHash, like in this unmerged commit for kotlin-interactive-shell: https://github.com/NixOS/nixpkgs/pull/522831/commits/7b6b4f8df72ba56b644e32c7719437e2ec6328e1