[
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/[email protected]/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
