You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2008/06/08 12:13:13 UTC

[jira] Updated: (MSHARED-17) Local Parent POM not found if specifies a directory

     [ http://jira.codehaus.org/browse/MSHARED-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg updated MSHARED-17:
-----------------------------------

    Fix Version/s: maven-doxia-tools 1.0

> Local Parent POM not found if <relativePath> specifies a directory
> ------------------------------------------------------------------
>
>                 Key: MSHARED-17
>                 URL: http://jira.codehaus.org/browse/MSHARED-17
>             Project: Maven Shared Components
>          Issue Type: Bug
>          Components: maven-doxia-tools
>         Environment: Maven 2.0.7, JDK 1.5.0_12, WinXP SP2
>            Reporter: Benjamin Bentmann
>            Assignee: Lukas Theussl
>            Priority: Minor
>             Fix For: maven-doxia-tools 1.0
>
>         Attachments: site-parent-pom.patch, site-parent-pom.patch
>
>
> The Maven core allows to specify a directory for the <relativePath> element in a module POM to locate the parent POM, e.g.{code:xml}<parent>
>     ...
>     <relativePath>../parent</relativePath>
> </parent>{code}will properly find the parent POM in "../parent/pom.xml". However, the Site plugin does not follow this lookup strategy:{code}
> [INFO] [site:site]
> [INFO] Unable to load parent project from a relative path: Could not find the model file '[SNIP]\..\parent'. for project unknown
> [INFO] Parent project loaded from repository.{code}
> This log output is actually from 2.0-beta-6-SNAPSHOT, 2.0-beta-5 outputs a different message but fails, too.
> The attached patch fixes this although I wonder whether this functionality is not already included somewhere in the Maven core (where is belongs IMHO).

-- 
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