Sorry about that. It appeared that the xml contained a different set (superset) of information than the logs. I'll attach xml from now on. Also, I wasn't sure that the list allowed attachments, thus the capture in the message to be safe.
I've got it now. On 4/17/06, Wayne Fay <[EMAIL PROTECTED]> wrote: > Just FYI... You don't need to include the full stacktrace when you > include the Txt or Xml file. > > And you don't really need to send both txt and xml files, just one or > the other. I guess the xml is best. > > Wayne > > > On 4/17/06, Julian Klappenbach <[EMAIL PROTECTED]> wrote: > > Still getting errors on test execution. This time, the output reads: > > > > ------------------------------------------------------- > > T E S T S > > ------------------------------------------------------- > > [surefire] Running > > org.apache.myfaces.tobago.renderkit.html.scarborough.standard.DateUnitTest > > [surefire] Tests run: 6, Failures: 1, Errors: 0, Time elapsed: 2.078 > > sec <<<<<<<< FAILURE !! > > [INFO] > > ------------------------------------------------------------------------ > > [ERROR] BUILD ERROR > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] There are test failures. > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Trace > > org.apache.maven.lifecycle.LifecycleExecutionException: There are test > > failures. > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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(DelegatingMethodAccessorImpl.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.MojoExecutionException: There are > > test failures. > > at > > org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:389) > > at > > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > > ... 16 more > > [INFO] > > ------------------------------------------------------------------------ > > > > > > I'm attaching the surefire logs. For now, I'll attempt to build with > > the flag to disable tests to see if I can get the themes built, and > > everything else dependent. > > > > -jjk > > > > > > >
