[
http://jira.codehaus.org/browse/SUREFIRE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145124#action_145124
]
Dan Tran commented on SUREFIRE-513:
-----------------------------------
I think i have a solution for this,
Have the surefire-integration-test/pom.xml to pass surefire.version, extracted
from ${project.version} to as system property,
have the main test to pass down the version down to all of its maven test
projects.
> Surefire Integration Test no longer valid when run with Maven 2.0.9+
> --------------------------------------------------------------------
>
> Key: SUREFIRE-513
> URL: http://jira.codehaus.org/browse/SUREFIRE-513
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.4.3
> Environment: windows, unix
> Reporter: Dan Tran
>
> The current surefire-intergration-test module does not define version tag in
> all of its test poms and therefore starting with maven 2.0.9, the integration
> tests use the implicit surefire 2.4.2.
> This means it does not run with dev version currently at 2.5-SNAPSHOT .
> Also any new features( ie SUREFIRE-511) cannot be tested either, it wont run
> with 2.4.2
> below is a list of fail tests that trigger this finding.
> Here is the summary
> Running org.apache.maven.surefire.its.TestNgSuiteXmlTest
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 11.89 sec <<<
> FA
> ILURE!
> Running org.apache.maven.surefire.its.TestNgSuiteXmlSingleTest
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.422 sec <<<
> FA
> ILURE!
> On Linux
> Failed tests:
> testTestNGSuite(org.apache.maven.surefire.its.TestNgSuiteXmlSingleTest)
> Tests in error:
>
> testTestNgSuiteXmlForkModeAlways(org.apache.maven.surefire.its.TestNgSuiteXmlT
> est)
--
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
