[MNG-4687] Maven should not warn about incorrect parent path when no relativePath is specified

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Auto Closed
• Affects Version/s: 3.0-beta-1
• Component/s: Logging
• Assignee: Unassigned
• Reporter: Paul Gier
• Created: 25/May/10 15:29
• Updated: 12/Jul/16 15:48
• Resolved: 12/Jan/16 20:12

Description

If a module pom uses a parent other than the one in the parent directory, maven logs a warning. In some cases it is necessary that a module pom has an external parent pom, and there is no way to refer to this external pom in the relativePath. If nothing is specified in the relativePath, Maven should not log the warning.

[WARNING] 'parent.relativePath' of POM org.maven.test:relative-path-parent:0.0.1-SNAPSHOT (/home/pgier/projects/MNG-relativePath/module-1/pom.xml) points at org.maven.test:relative-path-test instead of org.apache.maven:maven-parent, please verify your project structure @ 

The attached zip reproduces the warning.

Issue Links

• is depended upon by: MNG-2026 Document how parent-child POM relationships, <modules/>, and <parent><relativePath/> works
• is duplicated by: MNG-5146 parent.relativePath Warning is very misleading
• is related to: MNG-4619 Issue warning in case parent.relativePath points at POM with different groupId/artifactId