maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Commented: (MSITE-261) Local Parent POM not found if <relativePath> specifies a directory
Date Sat, 12 Jan 2008 09:26:57 GMT


Benjamin Bentmann commented on MSITE-261:

A simpler workaround should be to just specify the path to the parent POM directly, e.g. "../parent/pom.xml"
instead of "../parent". That's how I successfully get the plugin to work properly.

> Local Parent POM not found if <relativePath> specifies a directory
> ------------------------------------------------------------------
>                 Key: MSITE-261
>                 URL:
>             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:
For more information on JIRA, see:


View raw message