[
http://jira.codehaus.org/browse/SUREFIRE-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144821#action_144821
]
Benjamin Bentmann commented on SUREFIRE-512:
--------------------------------------------
This change was introduced to fix SUREFIRE-491.
You could try a configuration like the following to achieve your goal
{code:xml}
<systemProperties>
<property>
<name>my.environment</name>
<value>${my.environment}</value>
</property>
</systemProperties>
{code}
i.e. use Surefire's {{systemProperties}} parameter to explicitly pass
properties through to the tests.
> Provided Properties no longer visible in Surefire-Tests
> -------------------------------------------------------
>
> Key: SUREFIRE-512
> URL: http://jira.codehaus.org/browse/SUREFIRE-512
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.4.3
> Environment: maven 2.0.9, windows xp, surefire-plugin 2.4.3
> Reporter: Jerome Waibel
>
> I have a super pom and several modules with code and tests. I run the super
> pom with some commandline like
> mvn -Dmy.environment=foo test
> which calls all tests in the modules.
> In the tests I refer to the goven property (by using spring's property
> placeholder). Up to surefire 2.4.2 all tests ran fine, since 2.4.3 the
> property isn't visible any more in the tests (${my.environment} is simply
> unknown).
--
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
