[jira] Closed: (MNG-3597) Using ${project.parent.basedir} in causes InvalidProjectModelException

["Brett Porter (JIRA)" <ji...@codehaus.org>]

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

Brett Porter closed MNG-3597.
-----------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 2.2.x (to be reviewed))

this isn't a documented expression to my knowledge, and relying on the parent being in the workspace (where it might be in the repository) is unreliable.

I suggest you might need a pattern like the following: http://brettporter.wordpress.com/2009/06/10/a-maven-friendly-pattern-for-storing-dependencies-in-version-control/

> Using ${project.parent.basedir} in <systemPath/> causes InvalidProjectModelException
> ------------------------------------------------------------------------------------
>
>                 Key: MNG-3597
>                 URL: http://jira.codehaus.org/browse/MNG-3597
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 2.0.8
>            Reporter: Jan Rudert
>
> Hi 
> although the Anttask <echo message="${project.parent.basedir}" /> prints out the proper path of my multiproject's root directory, I get an InvalidProjectModelException If I try to use it in the <systemPath/> element of a dependency like this:
>  <dependency> 
>       <groupId>org.company.my</groupId>  
>       <artifactId>xyz</artifactId>  
>       <version>1.0</version>
>       <scope>system</scope>
>       <systemPath>${project.parent.basedir}/path/to/xyz.jar</systemPath>
>     </dependency>
> Also mvn help:effective-pom resolves that property if not used in <systemPath/>

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