You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andreas Sewe (JIRA)" <ji...@codehaus.org> on 2010/06/10 11:31:12 UTC

[jira] Created: (MASSEMBLY-487) Introduce ${artifact.properties} counterpart for ${project.properties}

Introduce ${artifact.properties} counterpart for ${project.properties}
----------------------------------------------------------------------

                 Key: MASSEMBLY-487
                 URL: http://jira.codehaus.org/browse/MASSEMBLY-487
             Project: Maven 2.x Assembly Plugin
          Issue Type: Improvement
    Affects Versions: 2.2-beta-5
            Reporter: Andreas Sewe


At the moment, interpolation in {{outputFileNameMapping}} allows access to the POM properties of the artifact in a {{dependencySet}} by means of {{${artifact.*}}}. Access to the (system) properties defined by the artifact's POM, however, is impossible; there is no {{${artifact.properties}}} counterpart for {{${project.properties}}}, even though it would solve some real-world problems for which no easy workaround is possible: http://www.mail-archive.com/users@maven.apache.org/msg109792.html.

That being said, this inconsistency is at the very least confusing, in particular as the documentation's distinction between POM properties and (system) properties is quite subtle.

-- 
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: (MASSEMBLY-487) Introduce ${artifact.properties} counterpart for ${project.properties}

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MASSEMBLY-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey closed MASSEMBLY-487.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2-beta-6
         Assignee: John Casey

> Introduce ${artifact.properties} counterpart for ${project.properties}
> ----------------------------------------------------------------------
>
>                 Key: MASSEMBLY-487
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-487
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.2-beta-5
>            Reporter: Andreas Sewe
>            Assignee: John Casey
>             Fix For: 2.2-beta-6
>
>
> At the moment, interpolation in {{outputFileNameMapping}} allows access to the POM properties of the artifact in a {{dependencySet}} by means of {{${artifact.*}}}. Access to the (system) properties defined by the artifact's POM, however, is impossible; there is no {{${artifact.properties}}} counterpart for {{${project.properties}}}, even though it would solve some real-world problems for which no easy workaround is possible: http://www.mail-archive.com/users@maven.apache.org/msg109792.html.
> That being said, this inconsistency is at the very least confusing, in particular as the documentation's distinction between POM properties and (system) properties is quite subtle.

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