You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kenney Westerhof (JIRA)" <ji...@codehaus.org> on 2006/05/01 00:08:18 UTC
[jira] Closed: (MRESOURCES-18) System properties and cmdline params
not filtered without filter file
[ http://jira.codehaus.org/browse/MRESOURCES-18?page=all ]
Kenney Westerhof closed MRESOURCES-18:
--------------------------------------
Assign To: Kenney Westerhof
Resolution: Fixed
Added a regression test it0105 in svn revision 398452.
This should ideally be moved to the plugin itself using the new framework, but after looking
at the complexity of the tests there I decided to hold off on converting. Aren't these 'old style' unit tests
much cleaner?
> System properties and cmdline params not filtered without filter file
> ---------------------------------------------------------------------
>
> Key: MRESOURCES-18
> URL: http://jira.codehaus.org/browse/MRESOURCES-18
> Project: Maven 2.x Resources Plugin
> Type: Bug
> Versions: 2.2, 2.1
> Reporter: Kenney Westerhof
> Assignee: Kenney Westerhof
> Fix For: 2.2
>
>
> If you have a src/main/resources/test.properties with the following content:
> param=${param}
> userhome=${user.home}
> and you define a resources section with filtering enabled for this, then running
> mvn process-resources -Dparam=PARAM
> yields a target/classes/test.properties where the properties are not filtered (i.e. the file is unchanged).
> When you define a <filters><filter>emptyfile</... and create 'emptyfile' with no content,
> the resource is properly filtered.
--
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