[SUREFIRE-491] All system properties from Maven process are copied to forked Surefire process

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.3
• Fix Version/s: 2.4.3
• Component/s: process forking
• Assignee: Unassigned
• Reporter: Daniel Fabulich
• Created: 28/Apr/08 16:03
• Updated: 04/Jun/09 10:12
• Resolved: 02/May/08 01:05

Description

Run a Surefire test with a different JVM using the -Djvm argument. For example, run the test with JDK 1.4 while running Maven with a 1.5 or 1.6 JVM.

Examine the XML file in target/surefire-reports corresponding to your test. The java.* properties will match the parent process, not the forked process. For example, <property name="java.version" value="1.6.0_02"/>.

Issue Links

• is depended upon by: SUREFIRE-510 surefire.test.class.path is not set when forkMode is always
• is duplicated by: SUREFIRE-461 -Xbootclasspath specified in <argLine> not passed to forked JVM
• is duplicated by: SUREFIRE-552 CLONE --Xbootclasspath specified in <argLine> not passed to forked JVM
• relates to: SUREFIRE-121 System properties set on the command line get clobbered
• relates to: SUREFIRE-512 Provided Properties no longer visible in Surefire-Tests