[
https://jira.codehaus.org/browse/MNG-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274931#comment-274931
]
Laird Nelson commented on MNG-4687:
-----------------------------------
No, please do not do automatic local resolution.
In a large project where pom.xml changes are made relatively frequently,
sometimes users do not do, say, an {{svn update}}. In such a case a local
build will reference what is effectively an out-of-date pom. If automatic
filesystem resolution were turned on, there would be no way to force Maven to
go get the pom from the repo. Unless, of course, I'm missing something.
> Maven should not warn about incorrect parent path when no relativePath is
> specified
> -----------------------------------------------------------------------------------
>
> Key: MNG-4687
> URL: https://jira.codehaus.org/browse/MNG-4687
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Logging
> Affects Versions: 3.0-beta-1
> Reporter: Paul Gier
> Priority: Minor
> Attachments: MNG-relativePath.zip
>
>
> 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.
> {noformat}
> [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 @
> {noformat}
> The attached zip reproduces the warning.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
