[ 
http://jira.codehaus.org/browse/MNG-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226812#action_226812
 ] 

Stan Devitt commented on MNG-4687:
----------------------------------

In our standard project structure we have a large number of projects which 
inherit their plugin configuration from a single centralized parent - loaded 
from the repository.  Separately the projects have one or more aggregator poms 
which resides in the directory directly above.

In this setup, we cannot use <relativePath>,  but maven 3 beta complains 
because the aggregator it finds is not the parent.

It is actually important to separate the roles of parent and aggregator - but 
the current design confuses them.


> 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

        

Reply via email to