(maven-site) branch master updated: Update release notes for validation changes

[kw...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 557761ba Update release notes for validation changes
557761ba is described below

commit 557761bae9596e991c0d2909c4f3e56c2116aad6
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Tue Oct 6 12:20:52 2026 +0200

    Update release notes for validation changes
    
    Clarified validation errors and added temporary disable option.
---
 content/markdown/docs/3.10.0/release-notes.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/content/markdown/docs/3.10.0/release-notes.md b/content/markdown/docs/3.10.0/release-notes.md
index c32a5731..d354fb12 100644
--- a/content/markdown/docs/3.10.0/release-notes.md
+++ b/content/markdown/docs/3.10.0/release-notes.md
@@ -109,7 +109,9 @@ now FAIL the build. Things like duplicated dependency entries or duplicated plug
 anymore. This aspect was not changed since Maven 3.1 lineage, and was really time to force users to clean up their
 POMs. The checks promoted to errors for the project being built are the 3.1 level ones: duplicated plugins, invalid
 characters in a version, malformed snapshot versions and reserved or malformed repository ids. Dependencies keep being
-validated at the minimal level. `relativePath` of a parent is validated as well, which no Maven 3.x version did so far.
+validated at the minimal level (and failure lead to transitive dependencies not being available). 
+`relativePath` of a parent is validated as well, which no Maven 3.x version did so far.
+To temporarily disable the stricter validation add `-Dmaven.resolver.validation=off` to your Maven incovation.
 
 ### Classpath ordering change