Re: [PR] Bump maven.version from 4.0.0-rc-5 to 4.0.0-rc-6 [maven-mvnd]

2026-08-04 Thread via GitHub


dependabot[bot] commented on PR #1715:
URL: https://github.com/apache/maven-mvnd/pull/1715#issuecomment-5180919450

   OK, I won't notify you again about this release, but will get in touch when 
a new version is available. You can also ignore all major, minor, or patch 
releases for a dependency by adding an [`ignore` 
condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore)
 with the desired `update_types` to your config file.
   
   If you change your mind, just re-open this PR and I'll resolve any conflicts 
on it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] Bump maven.version from 4.0.0-rc-5 to 4.0.0-rc-6 [maven-mvnd]

2026-08-04 Thread via GitHub


slachiewicz closed pull request #1715: Bump maven.version from 4.0.0-rc-5 to 
4.0.0-rc-6
URL: https://github.com/apache/maven-mvnd/pull/1715


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



[PR] Bump maven.version from 4.0.0-rc-5 to 4.0.0-rc-6 [maven-mvnd]

2026-08-04 Thread via GitHub


dependabot[bot] opened a new pull request, #1715:
URL: https://github.com/apache/maven-mvnd/pull/1715

   Bumps `maven.version` from 4.0.0-rc-5 to 4.0.0-rc-6.
   Updates `org.apache.maven:maven-plugin-api` from 4.0.0-rc-5 to 4.0.0-rc-6
   
   Updates `org.apache.maven:maven-model` from 4.0.0-rc-5 to 4.0.0-rc-6
   
   Updates `org.apache.maven:maven-core` from 4.0.0-rc-5 to 4.0.0-rc-6
   
   Updates `org.apache.maven:maven-resolver-provider` from 4.0.0-rc-5 to 
4.0.0-rc-6
   
   Updates `org.apache.maven:maven-embedder` from 4.0.0-rc-5 to 4.0.0-rc-6
   
   Updates `org.apache.maven:maven-cli` from 4.0.0-rc-5 to 4.0.0-rc-6
   
   Updates `org.apache.maven:maven-api-di` from 4.0.0-rc-5 to 4.0.0-rc-6
   
   Updates `org.apache.maven:maven-jline` from 4.0.0-rc-5 to 4.0.0-rc-6
   
   Updates `org.apache.maven:maven-logging` from 4.0.0-rc-5 to 4.0.0-rc-6
   
   Updates `org.apache.maven:apache-maven` from 4.0.0-rc-5 to 4.0.0-rc-6
   
   Release notes
   Sourced from https://github.com/apache/maven/releases";>org.apache.maven:apache-maven's 
releases.
   
   Maven 4.0.0-rc-6
   Notes
   This new release candidate of Maven 4 is released to get feedback from 
users.
   Maven 4 has restricted a few things compared to Maven 3, so make sure to run 
the https://maven.apache.org/tools/mvnup.html#Plugin_Compatibility_.26_Upgrades";>mvnup
 tool before trying your project with Maven 4.
   Issues fixed since RC-5
   All known issues reported in the RC-5 release notes have been fixed:
   
   Bean configuration bug — field accessibility state was 
cached globally, causing plugin configuration injection failures. Fixed in https://redirect.github.com/apache/maven/pull/11433";>#11433.
   Concurrency issue in the v4 API — a 
ConcurrentModificationException was fixed in https://redirect.github.com/apache/maven/pull/11429";>#11429.
   BOM packaging — consumer POM conversion for BOM 
projects now correctly preserves dependency versions. Fixed in https://redirect.github.com/apache/maven/pull/11464";>#11464.
   macOS Gatekeeper — the extracted JLine native binaries 
that triggered Gatekeeper have been removed from the distribution (https://redirect.github.com/apache/maven/pull/11997";>#11997). The 
xattr workaround from RC-5 is no longer needed.
   
   Known compatibility issues
   The following are known compatibility issues when using Maven 4. Running
   https://maven.apache.org/tools/mvnup.html";>mvnup 
before building with
   Maven 4 will fix many common plugin version issues automatically. The issues
   below are those that require manual intervention or upstream fixes.
   Stricter POM validation
   Maven 4 enforces stricter validation than Maven 3. Projects may need to 
fix their POMs:
   
   Duplicate XML elements — duplicate 
, , etc. are now 
rejected (Duplicated tag error). Fix the source POM.
   Duplicate dependency declarations — same 
groupId:artifactId declared twice is now rejected (must be 
unique).
   Uninterpolated expressions — ${...} 
expressions in repository URLs, distribution management IDs, and other fields 
that Maven 3 silently accepted are now rejected.
   Invalid XML in transitive POMs — illegal processing 
instructions or undeclared namespace prefixes in transitive POMs cause 
Non-parseable POM errors.
   Properties in  paths — Maven 
4 no longer interpolates properties like ${spark.version} in 
 elements at POM reading time.
   CI-friendly versions — projects using 
${revision} without flatten-maven-plugin may hit 
missing dependency version errors.
   Invalid Collect Request — transitive dependencies with 
uninterpolated ${...} version expressions are rejected.
   
   Transitive dependency resolution changes
   Maven 4's TransitiveDependencyManager applies 
dependencyManagement at all transitive depths (Maven 3 only 
applied it at the first level). This is intentional but can change resolved 
versions:
   
   Dependencies previously on the classpath may disappear — add explicit 
declarations. See https://redirect.github.com/apache/maven/issues/12302";>#12302.
   maven-enforcer-plugin version rules may trigger due to 
downgraded transitive versions.
   license-maven-plugin may report new transitive dependencies 
not in the allow-list.
   Karaf feature verification may fail due to OSGi bundle version 
mismatches.
   
   Plugin and extension compatibility
   Some plugins and extensions require specific versions for Maven 4:
   
   Quarkus — versions before 3.20 use 
ServiceLocator/RepositorySystem patterns incompatible 
with Maven 4's Sisu-based DI. Upgrade to Quarkus 3.20+.
   Tycho — versions before 5.0 use Guice/Sisu injection 
patterns broken by Maven 4. Upgrade to Tycho 5.0.3+.
   Develocity Maven extension — fails to initialize due to 
SLF4J classloading changes (ClassNotFoundException: 
SimpleLogger).
   
   
   
   ... (truncated)
   
   
   Commits
   
   https://github.com/apache/maven/commit/6a8189b24518daa120539fa41ce12f2b48ec09a8";>6a8189b