chore(repo): use @nx/maven to build @nx/maven

[MaxKless]

Current Behavior

there is an install target calling ./mvnw directly

Expected Behavior

we use the @nx/maven plugin for generating maven targets

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
nx-dev	Ready	Preview	Nov 26, 2025 9:36am

[netlify]

✅ Deploy Preview for nx-docs ready!

Name	Link
🔨 Latest commit	a97e635
🔍 Latest deploy log	https://app.netlify.com/projects/nx-docs/deploys/6926c8cd0bb2220008304625
😎 Deploy Preview	https://deploy-preview-33412--nx-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 4d25475

Command	Status	Duration	Result
nx affected --targets=lint,test,test-kt,build,e...	❌ Failed	33m 11s	View ↗
nx run-many -t check-imports check-lock-files c...	✅ Succeeded	2m 44s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	11s	View ↗
nx-cloud record -- nx format:check	✅ Succeeded	1s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	<1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-11-25 13:16:49 UTC

[graphite-app]

Version mismatch detected: package.json specifies @nx/maven: 22.1.0-rc.3 but pnpm-lock.yaml has locked version 22.1.0-rc.2. This mismatch will cause the wrong version to be installed.

# Fix by running:
pnpm install
# This will update the lockfile to match package.json

The lockfile must be regenerated to match the version specified in package.json to ensure consistent installations across environments.

Spotted by Graphite Agent



Is this helpful? React 👍 or 👎 to let us know.

[AgentEnder]

Remove?

[MaxKless]

for sure once debugging is done I'll remove it 👍

[nx-cloud]

Nx Cloud is proposing a fix for your failed CI:

These changes fix the Maven plugin resolution error by enabling installation of the parent POM (dev.nx:nx-parent:pom:0.0.10) to the local Maven repository. When the e2e tests initialize @nx/maven, Maven needs to resolve the parent POM that the maven-plugin references, and with maven.install.skip=false, the parent POM will now be available in the local repository instead of failing with "artifact not found" errors.

diff --git a/pom.xml b/pom.xml
index 60d8dd088b..852bf6c8ea 100644
--- a/pom.xml
+++ b/pom.xml
@@ -41,7 +41,7 @@
   <properties>
     <!-- Skip deploying parent POM -->
     <maven.deploy.skip>true</maven.deploy.skip>
-    <maven.install.skip>true</maven.install.skip>
+    <maven.install.skip>false</maven.install.skip>
     <maven.gpg.skip>true</maven.gpg.skip>
 
     <!-- Build Properties -->

  

Or Apply changes locally with:

npx nx-cloud apply-locally 5cj7-BKeu

Apply fix locally with your editor ↗   View interactive diff ↗

_{🎓 Learn more about Self-Healing CI on nx.dev}