Odin Hole Standal created SUREFIRE-965:
------------------------------------------
Summary: Changed behaviour for Maven properties from surefire
2.12.4 to 2.13
Key: SUREFIRE-965
URL: https://jira.codehaus.org/browse/SUREFIRE-965
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.13
Environment: Maven 3.0.4
JDK 1.7.0_10
Windows
Reporter: Odin Hole Standal
Priority: Minor
We just upgraded Surefire from 2.12.4 to 2.13 and witnessed a change in
behaviour with respect to system properties defined in Maven profiles.
Our build is a multi-module one with a nested structure. In our parent
project, we define profiles that set a system property to either 'A' or
'B'. Our tests rely on this system property being set to either 'A' or 'B'
across all tests in all modules.
However, when we upgraded to 2.13 and ran tests with profile 'A', suddenly
one of the modules in the build changed the property from 'A' to 'B'.
Is there any changes between 2.12.4 and 2.13 that might explain this
behaviour? I could not find any suspects in either the code or the change
list.
I'm sorry, but I can't share the build configuration.
Sincerely
--
Odin Hole Standal
--
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
