To check what Nisse injects one can use ./mvnw -V validate -N -Dnisse.dump, and the relevant snippet:

[INFO] Nisse injecting 34 properties into User Properties
[INFO] os.detected.arch=x86_64
[INFO] nisse.os.release.version=42
[INFO] nisse.jgit.author=Tamas Cservenak <tamas@cservenak.net>
[INFO] nisse.mvn.minor=0
[INFO] nisse.os.version.minor=14
[INFO] os.detected.release.like.fedora=true
[INFO] nisse.os.version=6.14
[INFO] os.detected.release=fedora
[INFO] os.detected.version.major=6
[INFO] nisse.mvn.qualifier=rc-4
[INFO] nisse.mvn.distributionShortName=Maven
[INFO] os.detected.release.version=42
[INFO] nisse.os.version.major=6
[INFO] nisse.jgit.committer=Tamas Cservenak <tamas@cservenak.net>
[INFO] nisse.mvn.majorMinor=4.0
[INFO] os.detected.bitness=64
[INFO] os.detected.name=linux
[INFO] nisse.os.bitness=64
[INFO] nisse.mvn.distributionId=apache-maven
[INFO] nisse.os.classifier=linux-x86_64
[INFO] nisse.mvn.version=4.0.0-rc-4
[INFO] nisse.os.release=fedora
[INFO] os.detected.version=6.14
[INFO] os.detected.classifier=linux-x86_64
[INFO] nisse.mvn.buildNumber=bed0f8174bf728978f86fac533aa38a9511f3872
[INFO] nisse.jgit.date=Thu Jun 19 14:20:37 2025 +0200
[INFO] nisse.os.release.like.fedora=true
[INFO] nisse.jgit.commit=dbc04846ef4bcdd4f5d1ef1dd040e17b3992223c
[INFO] os.detected.version.minor=14
[INFO] nisse.mvn.major=4
[INFO] nisse.mvn.distributionName=Apache Maven
[INFO] nisse.os.name=linux
[INFO] nisse.mvn.patch=0
[INFO] nisse.os.arch=x86_64

The os.detected.* properties are caused by "os-detector compatibility mode". Nisse by default uses nisse.<src>.<prop> format, so for example nisse.os.release.version=42 is Nisse injected and os.detected.release.version=42 is "os detector" key present due enabled compatibility mode.

Are there any plans to migrate to Central Portal publishing? 😉

And just to clarify: this PR contains nothing "Maven 4 specific" except the wrapper.properties bit. This PR also cleans up the Netty build for Maven 3. I'd recommend using Maven 3.9.9 in wrapper if this gets merged, as 3.9.10 has issues with reactor reduction (-pl etc), and 3.9.11 is on the way.

Are there any plans to migrate to Central Portal publishing? 😉

We already do in 4.2 and 4.1 branch

Well, personally I'd stay away from those two plugins, they meddle too much with Maven and project internals, and also has bad reputation regarding maintenance (well, their predecessors had for sure). Naturally, I'd warmly recommend Njord instead, that does not meddle with your build and Maven, plus it supports local staging as well that may come handy.

Well, personally I'd stay away from those two plugins, they meddle too much with Maven and project internals, and also has bad reputation regarding maintenance (well, their predecessors had for sure). Naturally, I'd warmly recommend Njord instead, that does not meddle with your build and Maven, plus it supports local staging as well that may come handy.

Will checkout Njord and see if this might be a good fit for us... For now I was just happy that we figured out how to move to maven central. The migration was far from smooth to say at least.