[
http://jira.codehaus.org/browse/MRESOURCES-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261482#action_261482
]
Petr Janata commented on MRESOURCES-99:
---------------------------------------
The workaround mentioned by Evgeny seems to be dependent on environment.
It works on my windows machine:
Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
Java home: c:\progs\java\jdk1.6.0_23_32bit\jre
Default locale: cs_CZ, platform encoding: Cp1250
OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
effective pom:
<timestamp>20110325-1614</timestamp>
But does not work on Jenkins CI server with Debian:
Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
Java version: 1.6.0_22, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.18.8-xenu", arch: "amd64", family: "unix"
effective pom:
<timestamp>${maven.build.timestamp}</timestamp>
> ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource
> filtering
> ---------------------------------------------------------------------------------------
>
> Key: MRESOURCES-99
> URL: http://jira.codehaus.org/browse/MRESOURCES-99
> Project: Maven 2.x Resources Plugin
> Issue Type: Improvement
> Components: interpolation
> Affects Versions: 2.3, 2.4
> Reporter: Thomas Champagne
>
> When filtering resources, ${project.baseUri} and ${maven.build.timestamp} are
> not expanded (remains unchanged in the output file).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
