[
http://jira.codehaus.org/browse/MNG-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234838#action_234838
]
Stan Devitt commented on MNG-4687:
----------------------------------
Current design of 3.0 betas assumes the pom of the directory above is a parent.
Good design separates the role of parent and aggregation and it makes sense
for the aggregator to be in the directory above, and for the parent to be a
stable configuration that come from the repository.
It would be very nice for this to be sorted out before the release of Maven 3.0.
> Maven should not warn about incorrect parent path when no relativePath is
> specified
> -----------------------------------------------------------------------------------
>
> Key: MNG-4687
> URL: http://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.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
