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:30:21 GMT

    [ http://jira.codehaus.org/browse/MRESOURCES-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221234#action_221234
] 

Andreas Sewe commented on MRESOURCES-99:
----------------------------------------

Actually, me last comment isn't true; the workaround does work with Maven 3. :-)

What happened was this: I followed the advice of http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html
and got burned by the fact that the manifest file include was the one from the *unfiltered*
source directory rather than from the filtered target directory. :-(

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