[MASSEMBLY-603] ${maven.build.timestamp} placeholder is not filtered

**[Igor Bljahhin](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=igor.bljahhin)** opened **[MASSEMBLY-603](https://issues.apache.org/jira/browse/MASSEMBLY-603?redirect=false)** and commented

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.

---

**Affects:** 2.3, 2.4

**Attachments:**
- [assembly-issue.zip](https://issues.apache.org/jira/secure/attachment/12714302/assembly-issue.zip) (_1.39 kB_)

**Issue Links:**
- [MRESOURCES-99](https://issues.apache.org/jira/browse/MRESOURCES-99) ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource filtering

4 votes, 8 watchers

Start with the attached assembly-issue test project and run "mvn clean package"; inspect index.html inside target/assembly-issue-0.0.1-SNAPSHOT-dist.zip to reproduce the filtering difference. Trace how assembly filtering handles project.version versus maven.build.timestamp, then verify that the timestamp is substituted in the generated archive.

Written by the indexing model from the issue text.