You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/01/09 21:29:01 UTC

[jira] Commented: (MNG-1927) ${project.build.directory} different in M2.0 & M2.0.1

    [ http://jira.codehaus.org/browse/MNG-1927?page=comments#action_55316 ] 

Brett Porter commented on MNG-1927:
-----------------------------------

its been noted that this isn't always the case, depending on environment. This leads me to believe it could be related to the introduction of environment variables in the expression evaluator.

> ${project.build.directory} different in M2.0 & M2.0.1
> -----------------------------------------------------
>
>          Key: MNG-1927
>          URL: http://jira.codehaus.org/browse/MNG-1927
>      Project: Maven 2
>         Type: Bug

>   Components: Inheritence and Interpolation
>     Reporter: Brett Porter
>     Priority: Blocker
>      Fix For: 2.0.2

>
>
> From Jens:
> In Maven 2.0 the value containes the whole absolute path to the target
> dir.
> C:\windows\system32\target
> With Maven 2.0.1 only:
> target\
> (Note: I was unable to reproduce this against 2.0, instead getting ${project.build.directory} verbatim, but I believe it should be an absolute path)

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org