Brian Demers created MNG-8708: --------------------------------- Summary: Maven 4 inaccurate error and warning with parent relative path of ../.. Key: MNG-8708 URL: https://issues.apache.org/jira/browse/MNG-8708 Project: Maven Issue Type: Improvement Affects Versions: 4.0.0-rc-3 Reporter: Brian Demers
Maven 4 (rc3) has inaccurate related path warnings (possibly behavior) when the relative path is ../.. (I assume the relative path issue effects any path to parent that is not the default (up one directory (`..`) In all cases below assume the parent pom is located at two levels above the child. If the child pom points to the parent using only a relativePath, this results in a warning of: > [WARNING] 'parent.relativePath' only specify relativePath or > groupId/artifactId in modelVersion 4.1.0 Expected behavior, no warning message. If the child pom points to the parent using a relative path AND groupId and artifactId, this results in the same warning (expected behavior) > [WARNING] 'parent.relativePath' only specify relativePath or > groupId/artifactId in modelVersion 4.1.0 If the child pom points to the parent pom using ONLY the groupId and artifactId, this results in an error: > [ERROR] 'parent.version' is missing. Expected behavior, POM to be resolved from the reactor (without needing a relative path or version) See demo for current behavior: https://github.com/bdemers/maven4-non-default-parent-path -- This message was sent by Atlassian Jira (v8.20.10#820010)