You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Odin Hole Standal (JIRA)" <ji...@codehaus.org> on 2013/02/22 10:39:13 UTC
[jira] (SUREFIRE-965) Changed behaviour for Maven properties from
surefire 2.12.4 to 2.13
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
[jira] (SUREFIRE-965) Changed behaviour for Maven properties from
surefire 2.12.4 to 2.13
Posted by "Odin Hole Standal (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320336#comment-320336 ]
Odin Hole Standal commented on SUREFIRE-965:
--------------------------------------------
I was afraid you'd say that :) I will see if I can reproduce it in a small project.
> 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
[jira] (SUREFIRE-965) Changed behaviour for Maven properties from
surefire 2.12.4 to 2.13
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/SUREFIRE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320330#comment-320330 ]
Kristian Rosenvold commented on SUREFIRE-965:
---------------------------------------------
I'm afraid we're going to need a little more than this to actually confirm/reproduce any such issue.
There wasn't really supposed to be any changes 2.12.4->2.13 that would make this happen. Something like a small test project to demonstrate the issue is going to be necessary.
> 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