Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
3.0-alpha-7
-
None
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.
Attachments
Issue Links
- relates to
-
MNG-4687 Maven should not warn about incorrect parent path when no relativePath is specified
- Closed