(maven) branch fix/MNG-8129-windows-invalid-path-3.10.x updated (f83f065e89 -> a664db5fd8)

[gn...@apache.org]

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

gnodet pushed a change to branch fix/MNG-8129-windows-invalid-path-3.10.x
in repository https://gitbox.apache.org/repos/asf/maven.git


 discard f83f065e89 [MNG-8129] Clarify relativePath validation comment
     new a664db5fd8 [MNG-8129] Clarify relativePath validation comment

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (f83f065e89)
            \
             N -- N -- N   refs/heads/fix/MNG-8129-windows-invalid-path-3.10.x (a664db5fd8)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:

(maven) 01/01: [MNG-8129] Clarify relativePath validation comment

[gn...@apache.org]

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

gnodet pushed a commit to branch fix/MNG-8129-windows-invalid-path-3.10.x
in repository https://gitbox.apache.org/repos/asf/maven.git

commit a664db5fd8fba5e8f9a9d13651f45ac289aa0af8
Author: Guillaume Nodet <gn...@gmail.com>
AuthorDate: Mon Aug 31 04:10:47 2026 +0200

    [MNG-8129] Clarify relativePath validation comment
    
    Address review: the banned characters are those reserved on
    Windows (NTFS), which cause InvalidPathException when resolved
    via java.nio.file.Path and typically indicate the user put a
    GAV coordinate instead of a filesystem path.
    
    Co-Authored-By: Claude Opus 4.6 <no...@anthropic.com>
---
 .../java/org/apache/maven/model/validation/DefaultModelValidator.java  | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java b/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
index 6cfed06ec7..bb8389d28d 100644
--- a/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
+++ b/maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
@@ -157,6 +157,9 @@ public void validateRawModel(Model m, ModelBuildingRequest request, ModelProblem
         } else if (request.getValidationLevel() >= ModelBuildingRequest.VALIDATION_LEVEL_MAVEN_2_0) {
             Severity errOn30 = getSeverity(request, ModelBuildingRequest.VALIDATION_LEVEL_MAVEN_3_0);
 
+            // [MNG-8129] Validate that relativePath does not contain characters reserved on Windows (NTFS).
+            // These cause InvalidPathException in Maven 4 when resolved via java.nio.file.Path, and typically
+            // indicate the user put a GAV coordinate (e.g. "g:a:v") instead of an actual filesystem path.
             if (parent != null
                     && parent.getRelativePath() != null
                     && !parent.getRelativePath().isEmpty()) {