You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Emmanuel Hugonnet (JIRA)" <ji...@codehaus.org> on 2006/12/18 16:54:43 UTC

[jira] Commented: (MNG-2201) Interpolation problem when using surefire

    [ http://jira.codehaus.org/browse/MNG-2201?page=comments#action_82875 ] 
            
Emmanuel Hugonnet commented on MNG-2201:
----------------------------------------

I have seen it too in SURFIRE 2.2 with Mavn 2.0x built the 16/12/2006 and you don't have this problem with environmentVariables which means it is a Properties interpolation issue only.
Sorry for the http://jira.codehaus.org/browse/SUREFIRE-60 that duplicates this issue.
Emmanuel

> Interpolation problem when using surefire
> -----------------------------------------
>
>                 Key: MNG-2201
>                 URL: http://jira.codehaus.org/browse/MNG-2201
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Inheritance and Interpolation
>    Affects Versions: 2.0, 2.0.1, 2.0.3, 2.0.2, 2.0.4
>            Reporter: Vincent Massol
>         Assigned To: John Casey
>            Priority: Critical
>             Fix For: 2.0.5
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> I've just tried the cargo build with the latest trunk versions of 2.0.4-SNAPSHOT and surefire plugin, and it seems there's some interpolation issue (I don't know if the problem is with the surefire plugin or with maven core).
> Here's what I have:
> {code:xml}
>   <build>
>     <pluginManagement>
>       <plugins>
>         <plugin>
>           <artifactId>maven-surefire-plugin</artifactId>
>           <configuration>
>             <forkMode>pertest</forkMode>
>             <systemProperties>
>               [...]
>               <property>
>                 <name>cargo.target.dir</name>
>                 <value>${project.build.directory}</value>
>               </property>
> [...]
> {code}
> It seems the ${project.build.directory} property is no longer getting resolved as I got a directory named ${project.build.directory} created.
> It used to work fine before.

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