David,
The JPA tests appear to have some sort of larger classpath issue that
is resulting in this failure. The one failure noted was:
Failed to invoke suite():java.lang.NoClassDefFoundError:
org.eclipse.jst.jpa.internal.utility.ClassTools org.eclipse.test.EclipseTestRunner$TestFailedException:
Failed to invoke suite():java.lang.NoClassDefFoundError:
org.eclipse.jst.jpa.internal.utility.ClassTools
No tests were actually run. Possibly a new classpath problem
somewhere, but I don't think we've changed anything in this area. It
looks like everything compiled so I'm not sure what the problem could
be. Any ideas?
Neil
David M Williams wrote:
Our I-builds are not ready for smoke
testing, yet, but the 1.5.3 maintenance stream is .... last 1.5.3 smoke
test of the year!
As for the I-builds, I will look
into
CSS JUnit failures
can JEE team look into their failing
tests? Is it EMF? JEM?
can JPA look into their failing
test?
the releng failing test is nothing
to
worry about (a not great test,
I'll
remove if I can not fix the test by end of day).
Thanks,
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
|
