Although the JDT problem we have found is major for us, I don't think it needs
to gate the smoke tests on other components unless you make use of JDT IType
and specifically IType.resolveType(). Similarly with other issue that appears
to be in common with JPT's failure.
--Cam
-Original M
The 7 failures in context.symbol.tests.AllTests are attributable to what
appears to be a new bug in JDT. I will characterize and attempt to workaround.
The intermittant failure in designtime.tests.AllTests is not reproducible
locally and seems related to the same type of problem that is occurri
I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=212186
to track this wsi unit test failure issue to be fixed in the future (after
this week's i build)
__
Amy Wu
905.413.2522, T/L 313-2522
[EMAIL PROTECTED]
Valentin Baciu/Toronto/[EMAIL PROTECTED]
Sent by:
I think I figured out what's going on here - in the Xerces 2.9 release
notes http://xerces.apache.org/xerces2-j/releases.html there's this note:
"Updated the schema loader so that it can now process schema documents
with an XML 1.1 declaration. [Michael Glavassevich] "
In our test suite we have
Helen,
I have commented out the intermittent JPT failure and released the
change.
Neil
Helen Zhang wrote:
Hi Team,
We continue to have JUnit failures
on
the I builds, 13 still, can teams please take a look at it and
provide
an update? Thank you!
http://download.eclipse.or
The WS-I Junit failures seem to be caused by the presence of the Xerces
2.9 bundle in the target, combined with a generous dependency range set to
org.apache.xerces;bundle-version="[2.8.0,3.0.0)" in the manifest for
org.eclipse.wst.wsi. Narrowing the range or removing Xerces 2.9 from the
target
Hi Team,
We continue to have JUnit failures on the I builds, 13 still, can teams
please take a look at it and provide an update? Thank you!
http://download.eclipse.org/webtools/committers/
Latest build=>
http://download.eclipse.org/webtools/committers/drops/R3.0/I-I20071206082655-2007120608265
