[
http://jira.codehaus.org/browse/MSITE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119609
]
Keith Naas commented on MSITE-261:
----------------------------------
This actually causes a major issue in a continuous build environment if you try
to run the site goal as part of the build. Since the project hasn't been
deployed to the remote repo yet, the site plugin attempts to access it on the
remote repo and the build fails.
The workaround is to run the build once without generating the site so that the
artifacts get into the repo. Then add the site goal later. Of course, the
site goal ends up using the last builds parent pom.xml, but normally its pretty
close.
> 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
> Priority: Minor
> Attachments: 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
