[EMAIL PROTECTED] wrote: > Jeremy wrote: > >>Thanks for the update. The unit-tests might be failing >>due to differences in the classpath between M1 and M2 >>- if you can post details of the failures we may be able >>to help debug them. > > > This turned out to be due to my not yet realizing how to > configure the surefire plugin to specify the include patterns > for picking up *TestCase.java. I fixed that :-) > > I'm now getting one failure in the runtime tests that I'm > not sure how to solve: > > junit.framework.AssertionFailedError: expected:<1> but was:<0> > at junit.framework.Assert.fail(Assert.java:47) > at junit.framework.Assert.failNotEquals(Assert.java:282) > at junit.framework.Assert.assertEquals(Assert.java:64) > at junit.framework.Assert.assertEquals(Assert.java:201) > at junit.framework.Assert.assertEquals(Assert.java:207) > at > org.apache.tuscany.container.java.assembly.impl.JavaImplementationTestCase.testHelloWorldWithSidefile(JavaImplementationTestCase.java:88) >
This might be because the xml sidefile (HelloWorldImpl.componentType) is not being copied to the classes directory. With M1 we had a custom resource definition which added **/*.componentType from the source tree to the set of resources to include. This was done as people felt that having the componentType file right next to the Java source was more intuitive than having it in a separate tree. I'd check target/classes and see if that file is there - if it isn't then this testcase will fail. -- Jeremy
