maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frédéric Camblor (JIRA) <j...@codehaus.org>
Subject [jira] Commented: (SUREFIRE-121) System properties set on the command line get clobbered
Date Sat, 03 Oct 2009 11:37:04 GMT

    [ http://jira.codehaus.org/browse/SUREFIRE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193293#action_193293
] 

Frédéric Camblor commented on SUREFIRE-121:
-------------------------------------------

+1
In a Test framework we've made, we're executing tests in eclipse by building maven.

The test framework allow to pass system properties in order to "filter" executed test by "categories"
Example :
mvn test -Dtest.categories=non-regression
(that will only execute non regression tests during maven test phase "a la" TestNG)

Since maven 2.0.10 (which aligned with surfire 2.4.3) we no longer can use this functionnality
...

Only workarounds for us is either :
- keep maven 2.0.9 (but this is crappy !!)
- use explicitely surefire 2.4.2 (impacts on most of our poms)
- define hacks in the poms, such as :
      <plugin>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>${surefire.version}</version>
        <configuration>
          <systemProperties>
            <test.categories>${test.categories}</test.categories>
          </systemProperties>
        </configuration>
      </plugin>
(impacts on most of our poms, too)

This is really crappy !!!

> System properties set on the command line get clobbered
> -------------------------------------------------------
>
>                 Key: SUREFIRE-121
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-121
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 2.0 (2.2 plugin)
>         Environment: Linux, Maven 2.0.4, Sun JDK 1.5U5, bash 3.0
>            Reporter: Brenton Leanhardt
>            Priority: Critical
>             Fix For: Future
>
>         Attachments: testargs.zip
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message