[
https://jira.codehaus.org/browse/MASSEMBLY-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362903#comment-362903
]
Mike Duigou commented on MASSEMBLY-603:
---------------------------------------
The workaround produces ${maven.build.timestamp} in the output for me and in
some contexts (NetBeans) the following error message:
[ERROR] Resolving expression: '${maven.build.timestamp}': Detected the
following recursive expression cycle in 'maven.build.timestamp':
[maven.build.timestamp]
This and http://jira.codehaus.org/browse/MRESOURCES-99 both deserve to be fixed.
> ${maven.build.timestamp} placeholder is not filtered
> ----------------------------------------------------
>
> Key: MASSEMBLY-603
> URL: https://jira.codehaus.org/browse/MASSEMBLY-603
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: filtering
> Affects Versions: 2.3, 2.4
> Reporter: Igor Bljahhin
> Priority: Minor
> Attachments: assembly-issue.zip
>
>
> When filtering files in assembly plugin most of placeholders are replaced
> with values,
> but Maven's property "maven.build.timestamp" (described here
> http://maven.apache.org/guides/introduction/introduction-to-the-pom.html in
> "Special Variables" section) is not substituted with value.
> Run "mvn clean package" in the test project and you will get
> "target/assembly-issue-0.0.1-SNAPSHOT-dist.zip" archive. Open index.html from
> archive and you will see that property "project.version" was replaced during
> assembly, but "maven.build.timestamp" was left untouched.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
