[ 
http://jira.codehaus.org/browse/MSITE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124234
 ] 
Benjamin Bentmann commented on MSITE-261:
-----------------------------------------

Andrew, you might face a different issue in your project (similar to Keith's 
one) than I originally reported here. Therefore, I suggest you open a new issue 
for this (I'm not sure how much awareness comments to closed issue receive). Be 
sure to name the versions of Maven and Maven Site Plugin you use. If possible, 
please attach a small demo project to reproduce this. This would greatly help 
to nail your problem down and come up with a solution.

> Local Parent POM not found if <relativePath> specifies a directory
> ------------------------------------------------------------------
>
>                 Key: MSITE-261
>                 URL: http://jira.codehaus.org/browse/MSITE-261
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>          Components: multi module
>    Affects Versions: 2.0-beta-5
>         Environment: Maven 2.0.7, JDK 1.5.0_12, WinXP SP2
>            Reporter: Benjamin Bentmann
>            Assignee: Lukas Theussl
>            Priority: Minor
>             Fix For: 2.0-beta-7
>
>         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

        

Reply via email to