| Summary: | Ant UI tests fail in the latest I-builds | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Michael Rennie <Michael_Rennie> |
| Component: | Ant | Assignee: | Platform-Ant-Inbox <platform-ant-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | aniefer, curtis.windatt.public, daniel_megert, markus.kell.r |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Michael Rennie
I only get the CCEs in I20110510-0800 when I check out org.eclipse.ant.launching and org.eclipse.ant.core from HEAD. When I close org.eclipse.ant.launching, the CCEs are gone and both classes use the same AntClassloader.
When org.eclipse.ant.launching is open, then
Class.forName(loggerClassname).getClassLoader()
returns a org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.
I have no idea why this happens.
Thanks for trying it out Markus, playing around with the code in InternalAntRunner, I forced it to use the AntClassLoader via: buildLogger = (BuildLogger) (Class.forName(loggerClassname, true, getClass().getClassLoader()).newInstance()); but it still failed. Probably related to bug 343455 comment #3. There are extra classpath entries in the dev.properties file for self hosted eclipse instances. This lets the osgi class loaders see classes they aren't supposed to. ClassCastExceptions are caused by mixing the classes loaded from OSGi classloaders with the ant URL classloader. I found this because PDE/Build tests also started failing locally. (In reply to comment #3) > > I found this because PDE/Build tests also started failing locally. I confirmed the patch on bug 343455 resolves the local test failures. marking as worksforme |