You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2010/07/15 20:43:32 UTC

[jira] Closed: (MANTTASKS-173) Value of project.build.finalName is not resolved

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

Herve Boutemy closed MANTTASKS-173.
-----------------------------------

       Resolution: Duplicate
    Fix Version/s: 2.1.1
         Assignee: Herve Boutemy

this is a duplicate of MANTTASKS-179

> Value of project.build.finalName is not resolved
> ------------------------------------------------
>
>                 Key: MANTTASKS-173
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-173
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>          Components: pom task
>    Affects Versions: 2.1.0
>         Environment: Windows
>            Reporter: Claudio Di Vita
>            Assignee: Herve Boutemy
>             Fix For: 2.1.1
>
>
> If Iuse the pom task in this way:
>    <artifact:pom id="maven.project" file="pom.xml" />
> the value of project.build.finalName is not resolved. If I access to property maven.project.build.finalName I only get ${project.artifactId}-${project.version}, instead I expect the real value (for example, myArtifact-1.0).
> In Maven Ant Tasks 2.0.10 this problem wasn't present.

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