[
http://jira.codehaus.org/browse/MRESOURCES-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann moved MNG-3417 to MRESOURCES-101:
---------------------------------------------------
Affects Version/s: (was: 2.0.8)
Component/s: (was: Maven Resources Filtering)
Key: MRESOURCES-101 (was: MNG-3417)
Project: Maven 2.x Resources Plugin (was: Maven 2)
> command-line properties not regarded sometimes
> ----------------------------------------------
>
> Key: MRESOURCES-101
> URL: http://jira.codehaus.org/browse/MRESOURCES-101
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Reporter: A
> Attachments: test_proj.zip
>
>
> I'm attaching a sample project to show properties specified on the
> command-line (CLI) not being regarded when filtering true. These are being
> regarded for other purposes though.
> Reproduce:
> $ mvn test
> $ cat target/test-classes/test.txt
> Contents: default
> $ mvn -P test.profile test
> $ cat target/test-classes/test.txt
> Contents: profile
> $ mvn -Dtest.property='overridden' clean verify
> Contents: default
> $ mvn -P test.profile -Dtest.property='overridden' clean verify
> Contents: profile
> As you see last two results should have been "Contents: overridden".
> The behavior is not completely broken though because if you try to set
> "test.include.pattern" then it works fine. Thus I set as component
> "filtering". This doesn't mean I've any idea where the issue lies. Test proj
> is a modified version of this on
> http://www.nabble.com/How-to-override-POM-properties-from-CLI-td15344487s177.html#a15605671
--
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
