[ http://jira.codehaus.org/browse/MSUREFIRE-105?page=comments#action_65256 ]
Jason Chaffee commented on MSUREFIRE-105: ----------------------------------------- Just tried it with no luck. I should add that these tests were working before applying the patch (on linux). Therefore, while this fixes the classpath issue, it has changed something to cause another issue. Let me explain what I am doing that is failing. In one project, I am creating a custom xsd and schema validation classes. In another project, I have the first project as a dependency and I have test that uses the javax.xml.validation package to validate a xml file that is import the schema from the first project. I will try to create a couple of simple test projects that reprduce the issue. I can either attach them to this bug or create a new bug...which is probably more appropriate. > Surefire plugin fails with certain dependencies in pom > ------------------------------------------------------ > > Key: MSUREFIRE-105 > URL: http://jira.codehaus.org/browse/MSUREFIRE-105 > Project: Maven 2.x Surefire Plugin > Type: Bug > Environment: This was tested with the trunk of surefire and > maven-surefire-plugin > Reporter: Jason Chaffee > Priority: Blocker > > > I added hibernate 3.0.1 to my pom and my tests that were working begin to > fail. In fact, they weren't even being run anymore. I was using testng > 4.7-jdk1.5. Here is the stacktrace: > [INFO] [surefire:test] > [INFO] Surefire report directory: > C:\workspace\svn-trunk\tva\packager\impl\targe > t\surefire-reports > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] There are test failures. > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > org.apache.maven.BuildFailureException: There are test failures. > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:555) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > fecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:454) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > 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) > Caused by: org.apache.maven.plugin.MojoFailureException: There are test > failures > . > at > org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugi > n.java:398) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:412) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:534) > ... 16 more -- 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
