Skip to content

Conversation

@aloubyansky
Copy link
Member

Fixes an issue found in Maven 4 RC5 (Maven resolver 2.11) discussed in #dev > Maven 4 ignoring our BOM? and quarkiverse/quarkus-logging-json#398

The fix in the resolver apache/maven-resolver#1702

@quarkus-bot quarkus-bot bot added the area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins label Dec 9, 2025
@quarkus-bot

This comment has been minimized.

@quarkus-bot
Copy link

quarkus-bot bot commented Dec 10, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit b3c50e4.

Failing Jobs

Status Name Step Failures Logs Raw logs Build scan
✔️ JVM Tests - JDK 17 Logs Raw logs 🚧
✔️ JVM Tests - JDK 21 Logs Raw logs 🚧
✔️ JVM Tests - JDK 21 Semeru Logs Raw logs 🚧
✔️ JVM Tests - JDK 25 Logs Raw logs 🚧
JVM Tests - JDK 17 Windows Build ⚠️ Check → Logs Raw logs 🚧

You can consult the Develocity build scans.

@gsmet gsmet merged commit ec03049 into quarkusio:main Dec 10, 2025
122 of 125 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.31 - main milestone Dec 10, 2025
@gsmet
Copy link
Member

gsmet commented Dec 10, 2025

@aloubyansky should we backport?

@aloubyansky
Copy link
Member Author

We could, I added the label. I don't consider it highly critical, given Maven 4 isn't final yet and the fix will be included in the next RC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins triage/backport triage/flaky-test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants