You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joe Stano (JIRA)" <ji...@codehaus.org> on 2010/03/02 18:30:56 UTC
[jira] Created: (MANTTASKS-179) Variables nested in pom.xml are not
being resolved
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
[jira] Commented: (MANTTASKS-179) Variables nested in pom.xml are
not being resolved
Posted by "Joe Stano (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MANTTASKS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212180#action_212180 ]
Joe Stano commented on MANTTASKS-179:
-------------------------------------
Using Ant 1.7.1
> 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
[jira] Commented: (MANTTASKS-179) Variables nested in pom.xml are
not being resolved
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (MANTTASKS-179) Variables nested in pom.xml are not
being resolved
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MANTTASKS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy closed MANTTASKS-179.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.1.1
Assignee: Herve Boutemy
fixed in [r964525|http://svn.apache.org/viewvc?view=revision&revision=964525]
this bug was introduced when upgrading Maven core dependency from 2.0.x to 2.2.x: interpolation is not automatic any more, it has to be called explicitely
> 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
> Assignee: Herve Boutemy
> Fix For: 2.1.1
>
>
> 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
[jira] Commented: (MANTTASKS-179) Variables nested in pom.xml are
not being resolved
Posted by "Joe Stano (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MANTTASKS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212170#action_212170 ]
Joe Stano commented on MANTTASKS-179:
-------------------------------------
A snippet of my project's pom.xml. These variables are not being resolved.
<project...>
...
<build>
<finalName>${artifactId}</finalName>
<directory>${basedir}/target</directory>
....
</build>
...
</project>
> 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
[jira] Updated: (MANTTASKS-179) Variables nested in pom.xml are not
being interpolated
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MANTTASKS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated MANTTASKS-179:
------------------------------------
Summary: Variables nested in pom.xml are not being interpolated (was: Variables nested in pom.xml are not being resolved)
> Variables nested in pom.xml are not being interpolated
> ------------------------------------------------------
>
> 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
> Assignee: Herve Boutemy
> Fix For: 2.1.1
>
>
> 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
[jira] Commented: (MANTTASKS-179) Variables nested in pom.xml are
not being resolved
Posted by "Joe Stano (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MANTTASKS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212175#action_212175 ]
Joe Stano commented on MANTTASKS-179:
-------------------------------------
I noticed I used inconsistent slashes in my example. I'm using forward slashes / for everything.
> 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