[SUREFIRE-121] System properties set on the command line get clobbered

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0 (2.2 plugin)
• Fix Version/s: 2.6
• Environment: Linux, Maven 2.0.4, Sun JDK 1.5U5, bash 3.0
• Assignee: Benjamin Bentmann
• Reporter: Brenton Leanhardt
• Created: 16/May/06 12:16
• Updated: 09/Jul/24 11:36
• Resolved: 01/Aug/10 13:32

Description

Some system properties get clobbered if you set them on the command line. For example,

mvn clean test -Dtest=LoginTest -Dselenium.user=test32

The 'test' system property will work, but the 'selenium.user' property will be null at runtime. I have tried:

• hard coding the system property in the unit test, this worked fine.
• setting the system properties in the pom file, this worked fine also.
• tried an older version of the surefire plugin, this worked fine.

Issue Links

• is duplicated by: SUREFIRE-564 [surefire] Command line parms not passed to tests on linux
• is related to: SUREFIRE-1385 System properties defined in the Surefire and Failsafe plugin configuration should override user properties
• is related to: SUREFIRE-491 All system properties from Maven process are copied to forked Surefire process
• relates to: SUREFIRE-635 System properties are not reported in xml files