You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/23 01:33:00 UTC
[jira] [Commented] (MASSEMBLY-603) ${maven.build.timestamp}
placeholder is not filtered
[ https://issues.apache.org/jira/browse/MASSEMBLY-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002042#comment-17002042 ]
Elliotte Rusty Harold commented on MASSEMBLY-603:
-------------------------------------------------
https://issues.apache.org/jira/browse/MRESOURCES-99 was fixed. Is this fixed too?
> ${maven.build.timestamp} placeholder is not filtered
> ----------------------------------------------------
>
> Key: MASSEMBLY-603
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-603
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: filtering
> Affects Versions: 2.3, 2.4
> Reporter: Igor Bljahhin
> Priority: Minor
> Labels: GoodForNewContributors
> 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
(v8.3.4#803005)