Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 3.0-alpha-7
-
Fix Version/s: 3.0-beta-1
-
Component/s: POM
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
While a version mismatch for the local POM at parent.relativePath is not unusual, discovering a POM with a completely different groupId or artifactId indicates an inconsistency between the project structure and the POM. We should tell users this via a warning to help fixing their setup and avoid potential confusion about parent resolution.
Issue Links
- relates to
-
MNG-4687
Maven should not warn about incorrect parent path when no relativePath is specified
-
Done in r930665.