[
http://jira.codehaus.org/browse/MASSEMBLY-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MASSEMBLY-256:
---------------------------------
Affects Version/s: 2.2-beta-1
Fix Version/s: (was: 2.2-beta-2)
2.2-beta-3
The problem is your use of the prefix 'project.' to refer to these properties.
I understand that the prefixes 'pom.' and 'project.' are commonly
interchangeable in Maven, and I'm adding code right now to add support for
'project.'
However, for the 2.2-beta-2 release, I don't think it's critical to add support
for project. expressions and re-start the entire voting process. I'd prefer to
push for a next release in short order, and get this one out with valid 'pom.'
expression support.
Can you verify that the example you're testing against will work if you use
${pom.properties.fileLocation}?
> Regression: pom properties are no longer expanded in descriptor.
> ----------------------------------------------------------------
>
> Key: MASSEMBLY-256
> URL: http://jira.codehaus.org/browse/MASSEMBLY-256
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1, 2.2-beta-2
> Environment: maven 2.0.8
> windows xp sp2
> Reporter: Mark Reynolds
> Assignee: John Casey
> Fix For: 2.2-beta-3
>
> Attachments: assembly-issue.zip
>
>
> Attached is a minimal project which demonstrates this issue.
> The pom contains a property:
> <project>
> ...
> <properties>
> <fileLocation>file/path</fileLocation>
> </properties>
> </project>
> The descriptor uses this property in specifying the output directory for a
> fileSet:
> <assembly>
> ...
> <fileSets>
> <fileSet>
> <directory>src/main/files</directory>
> <outputDirectory>${fileLocation}</outputDirectory>
> </fileSet>
> </fileSets>
> </assembly>
> In versions 2.1, 2.2-beta-1, and 2.2-SNAPSHOT of the assembly plugin, this
> property is expanded so the resulting archive has files in file/path/....
> In the latest 2.2-beta-2-SNAPSHOT, the resulting archive has files in
> ${fileLocation}/...
--
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
