Repository navigation
fix(repo): unblock Windows and FreeBSD publish builds after @nx/maven self-build - #37379
Open
FrozenPandaz wants to merge 3 commits into
Open
FrozenPandaz wants to merge 3 commits into
FrozenPandaz wants to merge 3 commits into
Conversation
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for nx-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
View your CI Pipeline Execution ↗ for commit dd74ab0
☁️ Nx Cloud last updated this comment at |
Contributor
|
Failed to publish a PR release of this pull request, triggered by @FrozenPandaz. |
FrozenPandaz
had a problem deploying
to
npm-registry
October 10, 2026 06:56 — with
GitHub Actions
Failure
FrozenPandaz
marked this pull request as ready for review
October 11, 2026 14:54
FrozenPandaz
force-pushed
the
fix/publish-maven-windows-freebsd
branch
from
October 11, 2026 14:55
6019461 to
30c4708
Compare
FrozenPandaz
changed the base branch from
master
to
fix/ultracache-native-node-reads
October 11, 2026 17:37
FrozenPandaz
added this pull request to stack #37384
October 11, 2026 17:38
FrozenPandaz
force-pushed
the
fix/publish-maven-windows-freebsd
branch
from
October 11, 2026 17:38
30c4708 to
a703780
Compare
Contributor
There was a problem hiding this comment.
Nx Cloud has identified a flaky task in your failed CI:
🔂 Since the failure was identified as flaky, we triggered a CI rerun by adding an empty commit to this branch.
🎓 Learn more about Self-Healing CI on nx.dev
… self-build Skip the asdf Maven plugin on Windows (mvnw.cmd is used instead) and install a JDK in the FreeBSD VM so mvnw can build the project graph.
The published nx-maven-plugin reports Windows project roots with backslashes, which breaks the project graph. The native builds don't need Maven projects.
Installing a JDK for the Maven graph left under 500 MB free after the build. Disable it like Gradle and .NET instead.
FrozenPandaz
force-pushed
the
fix/publish-maven-windows-freebsd
branch
from
October 11, 2026 21:31
a703780 to
dd74ab0
Compare
This branch had an error being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Current Behavior
Since #33412 added
asdf:mise-plugins/mise-maventomise.tomland the@nx/mavenplugin tonx.json, the publish workflow fails on:nx-maven-pluginreports project roots with backslashes, so the project graph fails with duplicate projects.@nx/mavenplugin runs./mvnwwhile building the project graph, and the VM has no JDK (The java(1) command does not exist in PATH nor is JAVA_HOME set).Canary has been red since 2026-10-07, and
24.0.0-beta.0failed on Windows.Expected Behavior
dotnet).NX_MAVEN_DISABLE=true. They only build native bindings, so they don't need the Maven graph. FreeBSD already disables Gradle and .NET this way; installing a JDK there instead left under 500 MB free after the build.The backslash bug itself is fixed in #37383. The Windows
NX_MAVEN_DISABLEcan be removed once that ships in a releasednx-maven-pluginand the rootpom.xmlis bumped.Verified with a publish dry-run: all build jobs pass (the Publish job is blocked by the
npm-registryenvironment rule for non-master branches, as expected).Related Issue(s)
N/A — CI breakage introduced by #33412.
View Polygraph session ↗