chore(maven): bump maven plugin version to 0.0.14#34505
Conversation
FrozenPandaz
requested review from
a team,
Coly010,
MaxKless,
lourw,
meeroslav and
vsavkin
as code owners
✅ 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. |
|
View your CI Pipeline Execution ↗ for commit 605f1eb
☁️ Nx Cloud last updated this comment at |
FrozenPandaz
force-pushed
the
maven-bump
branch
2 times, most recently
from
d08ee65 to
c98800a
Compare
![nx-cloud[bot]](https://avatars.githubusercontent.com/in/80458?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
FrozenPandaz
force-pushed
the
maven-bump
branch
from
c2ca6a3 to
c5f57ed
Compare
There was a problem hiding this comment.
Important
At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.
Nx Cloud has identified a possible root cause for your failed CI:
Our e2e test is failing because the Maven plugin version 0.0.14 has not yet been published to Maven Central (https://repo.maven.apache.org/maven2). The code changes are correct, but we need to wait for the artifact publishing process to complete before these tests can pass.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
The install target was building the entire reactor, including batch-runner modules. This caused a race condition when maven-batch-runner:package ran in parallel, as both tasks competed over the same target directories.
FrozenPandaz
force-pushed
the
maven-bump
branch
from
110a1b4 to
605f1eb
Compare
2 participants
Current Behavior
The Maven plugin is on version
0.0.13.Expected Behavior
The Maven plugin is bumped to version
0.0.14, with a migration generated for Nx22.6.0-beta.1.