[
http://jira.codehaus.org/browse/SUREFIRE-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128811#action_128811
]
Dan Fabulich commented on SUREFIRE-463:
---------------------------------------
Well, I think I like the idea of this patch, but I'm a bit creeped out by it,
because I can't reproduce your example. We've got a sample integration test
that uses suiteXmlFile and it passes (and, more generally, I use that feature
all the time). I tried just pasting your snippet into that test and running it
with "-P browser", hoping that maybe the problem was with the use of a profile,
but no, the test ran just fine on my machine.
Can you provide a minimal example Maven project that reproduces the problem?
We can check that into the integration test suite to make sure that issues like
this don't crop up again in the future.
> ClassCastException when using testng suiteXmlFile
> -------------------------------------------------
>
> Key: SUREFIRE-463
> URL: http://jira.codehaus.org/browse/SUREFIRE-463
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.4.2
> Environment: linux 2.6.22-1-mepis-smp
> Reporter: Andreas Andreou
> Attachments: SUREFIRE-463__handle_TestNG_xmlTestSuites.patch
>
>
> The related pom part is:
> <profile>
> <id>browser</id>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <suiteXmlFiles>
>
> <suiteXmlFile>src/test/resources/testng-browser.xml</suiteXmlFile>
> </suiteXmlFiles>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </profile>
> Issuing mvn -Pbrowser test results in the exception:
> java.lang.ClassCastException: java.io.File cannot be cast to java.lang.String
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesForkPerTestSet(SurefireBooter.java:403)
> at
> org.apache.maven.surefire.booter.SurefireBooter.run(SurefireBooter.java:249)
> at
> org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:492)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Any workarounds for this?
--
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
