[MRESOURCES-39] Filtering fails for command line properties

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.2
• Fix Version/s: 2.3
• Environment: maven-2.0.4 and maven-2.0.5; Mac OS X
• Assignee: Olivier Lamy
• Reporter: Matt Brozowski
• Created: 17/Jan/07 09:58
• Updated: 25/Jul/14 04:33
• Resolved: 06/Sep/08 17:45

Description

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.

Issue Links

• depends upon: MRESOURCES-56 use (and release) the maven-filtering component
• is duplicated by: MRESOURCES-85 command line cannot overwrite pom properties
• is duplicated by: MRESOURCES-101 command-line properties not regarded sometimes
• is related to: MRESOURCES-6 When filtering, properties defined in <project><properties> should be allowed as well.