[
https://jira.codehaus.org/browse/MASSEMBLY-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314542#comment-314542
]
Anton Koscejev commented on MASSEMBLY-603:
------------------------------------------
Currently a workaround that works for me:
{code}
<properties>
<!-- workaround for http://jira.codehaus.org/browse/MASSEMBLY-603 -->
<maven.build.timestamp>${maven.build.timestamp}</maven.build.timestamp>
</properties>
{code}
> ${maven.build.timestamp} placeholder is not filtered
> ----------------------------------------------------
>
> Key: MASSEMBLY-603
> URL: https://jira.codehaus.org/browse/MASSEMBLY-603
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Components: filtering
> Affects Versions: 2.3
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
