maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <j...@codehaus.org>
Subject [jira] (MASSEMBLY-603) ${maven.build.timestamp} placeholder is not filtered
Date Tue, 11 Feb 2014 21:54:57 GMT

     [ https://jira.codehaus.org/browse/MASSEMBLY-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Heinz Marbaise updated MASSEMBLY-603:
------------------------------------------

    Affects Version/s: 2.4

> ${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)

Mime
View raw message