Yes, it now builds successfully, thanks Dan.

Now, unfortunately I am getting another error:

-------------------------------------------------------
T E S T S
-------------------------------------------------------
[surefire] Running org.apache.tuscany.binding.celtix.assembly.WebServiceAssembly
FactoryTestCase
[surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.13 sec
[surefire]

[surefire] Running org.apache.tuscany.binding.celtix.handler.io.NodeDataWriterTe
stCase
[surefire] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.843 sec
[surefire]
[surefire] testWriteWrapper(org.apache.tuscany.binding.celtix.handler.io.NodeDat
aWriterTestCase)  Time elapsed: 1.753 sec  <<< ERROR!
javax.xml.ws.WebServiceException: java.lang.ClassNotFoundException: com.sun.org.
apache.xerces.internal.dom.DOMImplementationSourceImpl
at org.apache.tuscany.binding.celtix.handler.io.NodeDataReader.readWrapp
er(NodeDataReader.java:78)
at org.apache.tuscany.binding.celtix.handler.io.NodeDataReader.readWrapp
er(NodeDataReader.java:22)
at org.apache.tuscany.binding.celtix.handler.io.NodeDataWriterTestCase.t
estWriteWrapper(NodeDataWriterTestCase.java:78)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
       at java.lang.reflect.Method.invoke(Method.java:615)
       at junit.framework.TestCase.runTest(TestCase.java:154)
       at junit.framework.TestCase.runBare(TestCase.java:127)
       at junit.framework.TestResult$1.protect(TestResult.java:106)
       at junit.framework.TestResult.runProtected(TestResult.java:124)
       at junit.framework.TestResult.run(TestResult.java:109)
       at junit.framework.TestCase.run(TestCase.java:118)
       at junit.framework.TestSuite.runTest(TestSuite.java:208)
       at junit.framework.TestSuite.run(TestSuite.java:203)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
       at java.lang.reflect.Method.invoke(Method.java:615)
at org.apache.maven.surefire.battery.JUnitBattery.executeJUnit(JUnitBatt
ery.java:242)
at org.apache.maven.surefire.battery.JUnitBattery.execute(JUnitBattery.j
ava:216)
at org.apache.maven.surefire.Surefire.executeBattery(Surefire.java:215)
       at org.apache.maven.surefire.Surefire.run(Surefire.java:163)
       at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
       at java.lang.reflect.Method.invoke(Method.java:615)
at org.apache.maven.surefire.SurefireBooter.runTestsInProcess(SurefireBo
oter.java:313)
at org.apache.maven.surefire.SurefireBooter.run(SurefireBooter.java:221)

at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:371)

at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:415)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:531)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:472)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:303)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:270)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:139)
       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:249)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
       at java.lang.reflect.Method.invoke(Method.java:615)
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: java.lang.ClassNotFoundException: com.sun.org.apache.xerces.internal.
dom.DOMImplementationSourceImpl
       at java.net.URLClassLoader.findClass(URLClassLoader.java:491)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:560)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:517)
at org.w3c.dom.bootstrap.DOMImplementationRegistry.newInstance(Unknown S
ource)
at org.apache.tuscany.binding.celtix.handler.io.NodeDataReader.getNodeSt
ream(NodeDataReader.java:93)
at org.apache.tuscany.binding.celtix.handler.io.NodeDataReader.readWrapp
er(NodeDataReader.java:58)
       ... 48 more


[surefire] Running org.apache.tuscany.binding.celtix.loader.WebServiceBindingLoa
derTestCase
[surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.26 sec
[surefire]


Results :
[surefire] Tests run: 3, Failures: 0, Errors: 1

[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(Defa
ultLifecycleExecutor.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:472)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:303)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:270)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:139)
       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:249)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
       at java.lang.reflect.Method.invoke(Method.java:615)
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 failur
es.
at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:389)

at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:415)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:531)
       ... 16 more
[INFO] -------------------------------------------------------------------------


Thanks for any help in advance.


----- Original Message ----- From: "Daniel Kulp" <[EMAIL PROTECTED]>
To: <[email protected]>
Cc: "Ignacio Silva-Lepe" <[EMAIL PROTECTED]>
Sent: Monday, May 08, 2006 4:58 PM
Subject: Re: Build Break?



Can you update and try again?   I copied the version from the yoko project
which has been tested with windows and unix.   Thus, in theory, it should
work.

This DOES point out that apparently no-body checked it on windows while it
was in the sandbox.   Not a huge deal, but in the future, we should
probably make sure that anything moved from sandbox to main IS tested on
a couple platforms.

Dan


Reply via email to