[
https://jira.codehaus.org/browse/MRESOURCES-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292562#comment-292562
]
Eric Miller commented on MRESOURCES-39:
---------------------------------------
Not sure where this issue is. I was using 2.5, but command line property
overrides do not work in that version. It works in version 2.4.
> Filtering fails for command line properties
> -------------------------------------------
>
> Key: MRESOURCES-39
> URL: https://jira.codehaus.org/browse/MRESOURCES-39
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: maven-2.0.4 and maven-2.0.5
> Mac OS X
> Reporter: Matt Brozowski
> Assignee: Olivier Lamy
> Priority: Critical
> Fix For: 2.3
>
> Attachments: filtering-bug.tar,
> maven-resources-plugin-prop-filtering-r630241.patch
>
>
> When passing a property on the command line to maven using -D it does not
> properly override values passed to filters.
> I have attached a sample project that defines a property in the pom.xml
> called 'filtered' This property is used as a filter in the
> filtered.properties file in src/main/filtered/filtered.properties. I have
> also included a test that gets passed the filtered property as a System
> property via the surefire plugin. It then loaded the filtered.properties
> file and tests to ensure the filters match.
> The tests pass when run as
> mvn test
> BUT if I run as
> mvn -Dfiltered=from-cmd-line teset
> They fail.
> I have also included the antrun plugin print its perspective on the value of
> the property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
