maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herve Boutemy (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MANTTASKS-179) Variables nested in pom.xml are not being resolved
Date Fri, 26 Mar 2010 22:41:23 GMT

    [ http://jira.codehaus.org/browse/MANTTASKS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215570#action_215570
] 

Herve Boutemy commented on MANTTASKS-179:
-----------------------------------------

ok, bug reproduced in [r928083|http://svn.apache.org/viewvc?view=revision&revision=928083]

> Variables nested in pom.xml are not being resolved
> --------------------------------------------------
>
>                 Key: MANTTASKS-179
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-179
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>          Components: pom task
>    Affects Versions: 2.1.0
>            Reporter: Joe Stano
>
> My build project parses a project's pom.xml to expose the data to various ant tasks.
 After parsing the pom.xml, the ant tasks use the normal variable syntax such as ${project.build.directory}
to dig into the pom's contents.
> The value of this specific element in my project is "${basedir}/target".  In 2.0.10,
the resulting value of this lookup will be fully resolved to the project's directory.  With
2.1.0, the value resolves to the literal "${basedir}/target" and the build fails.
> 2.1.0 failure with a ${project.build.directory} value of "${basedir}\target": 
> java.io.FileNotFoundException: c:\Projects\ProjectName\${basedir}\target\version.jsp
(The system cannot find the path specified)

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

        

Mime
View raw message