You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andreas Sewe (JIRA)" <ji...@codehaus.org> on 2010/05/14 16:10:12 UTC
[jira] Commented: (MRESOURCES-99) ${project.baseUri} and
${maven.build.timestamp} are not expanded by resource filtering
[ http://jira.codehaus.org/browse/MRESOURCES-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221233#action_221233 ]
Andreas Sewe commented on MRESOURCES-99:
----------------------------------------
I couldn't get Evgeny's workaround to work on Maven 3.0-alpha-7 and 3.0-beta-1. According to {{help:effective-pom}} the property {{${maven.build.timestamp}}} does get interpolated in the POM, but resource filtering (which affects the file in question, at least according to {{mvn -X}}) doesn't work.
> ${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
> 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