maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Sewe (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRESOURCES-99) ${project.baseUri} and ${maven.build.timestamp} are not expanded by resource filtering
Date Fri, 14 May 2010 14:10:12 GMT

    [ 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

        

Mime
View raw message