@pyrox:pyrox.dev I've updated the PR that introduces the default plugins repo. I've addressed review feedback and added two commits that handle unrelated package build failures. Not sure if that should be separate PRs. I wanted a state where nixpkgs-review passes with out having to wait for other PRs to be merged first.

I've also rebased onto main and ran into an issue with the new maven_4 package that was merged recently: unfortunately they changed completely how default plugin versions are handled inside maven. Previously it was some xml files, which made it easy to extract this data. Now it' constants in Java code which are constructed by concatination of other constants. So there's no easy grep in the java sources solution for maven_4.
I didnt want to blow the scope of the PR, so I decided to add some logic that make maven_4 behave like maven_3 did before: essentially package dependency FOD hashes need to be updated when maven_4 package is updated. I want to address this in a follow up PR.

Link: https://github.com/NixOS/nixpkgs/pull/527061

Folks, https://github.com/NixOS/nixpkgs/pull/527061 is ready to be integrated from my PoV. I fixed the two failing packages and I tested the whole update flow end to end:

• run update script on maven updates maven's src coords as well as the default plugins repo hash.
• rebuilding a downstream package works without recalculating that package's mvnHash.

I'd relly like to get that in so we can focus on the maven version update that was blocked because of many downstream packages breaking with mvnHash missmatches.