Simon,

Did you find any leads on this issue? Surprisingly I stumbled across a similar problem in my 1.x branch. I am able to run a JUnit test case for Holders (TUSCANY-2332) in my Eclipse environment using "JUnit run as", but when I run it externally in my command line Maven environment I get new exceptions that I did not see prior. At this point I am doing a clean build of my entire Maven tree to see if that fixes the issue.


Others,

Any good general pointers for why a JUnit test would run in Eclipse but not in the Maven environment.


Simon Laws wrote:
On Mon, Jan 12, 2009 at 2:07 PM, Dan Becker <[email protected]> wrote:

Simon Laws wrote:

Can someone with 1.x loaded in Eclipse try running the DomainManager unit
test. When I run it the namespace in the sca-contributions.xml file is not
read correctly by wstx which causes a failure. This works OK when run from
maven. I have local change so I want to be sure that it's not something
I've
done that's causing the problem.

Hello Simon,

Running from the 1.x branch, I also get a clean run from Maven, but a
failure in testDeployables in the DomainManagerTestCase.

junit.framework.ComparisonFailure: null expected:<composite:store;[
http://store];store> but was:<composite:store;[];store>
       at junit.framework.Assert.assertEquals(Assert.java:81)
       at junit.framework.Assert.assertEquals(Assert.java:87)
       at
org.apache.tuscany.sca.domain.manager.impl.DomainManagerTestCase.testDeployables(DomainManagerTestCase.java:114)

This is using IBM 1.6 JDK.
--
Thanks, Dan Becker


Thanks Dan, I'm not going mad then. I see the same.  I've been wracking my
brains trying to work out how the change I have made could be causing this.
It seems though it's just that I've never run this particular test from
Eclipse. I feels like a library version problem. hard to say at the moment.

Simon



--
Thanks, Dan Becker

Reply via email to