Community
Participate
Working Groups
Build I20030618 1. Create a new workspace 2. Turn off autobuild 3. Import all the Eclipse plug-ins from the I20030618 drop as binary plug-ins 4. Replace some of these projects with ones from CVS (in my case, I was loading the projects for the JFace, UI, and Text plug-ins). 5. Build Observe: There are build errors. It complains that a bunch of the projects cannot be build (missing .classpath files). This was reported in bug 39186, which I'm trying to workaround. 6. Delete all the binary plug-in projects from the workspace. 7. Go to the PDE > Target Platform preference. 8. Select this application 9. Select Not in workspace Observe: All 66 plug-ins are selected. Expectation: It should have excluded the 10 in the workspace. 10. Manually deselect the ones that are already in workspace. 11. OK 12. Project > ReBuild All Observe: There are build problems: Build problems Errors during build. org.apache.xerces.parsers.DOMBuilderImpl: method setFeature (Ljava/lang/String;Z)V not found org.apache.xerces.parsers.DOMBuilderImpl: method setFeature (Ljava/lang/String;Z)V not found org.apache.xerces.parsers.DOMBuilderImpl: method setFeature (Ljava/lang/String;Z)V not found java.lang.NullPointerException encountered while running org.eclipse.pde.internal.builders.ExtensionPointSchemaBuilder. org.apache.xerces.parsers.DOMBuilderImpl: method setFeature (Ljava/lang/String;Z)V not found org.apache.xerces.parsers.DOMBuilderImpl: method setFeature (Ljava/lang/String;Z)V not found org.apache.xerces.parsers.DOMBuilderImpl: method setFeature (Ljava/lang/String;Z)V not found org.apache.xerces.parsers.DOMBuilderImpl: method setFeature (Ljava/lang/String;Z)V not found java.lang.NullPointerException encountered while running org.eclipse.pde.internal.builders.ExtensionPointSchemaBuilder.
There is no guarantee what state the projects you checked out from CVS are in after the buggy CVS checkout. could you delete those as well and try again? Things should be fine then.
I deleted the workspace repeated and started over. I turned autobuild off. I did a checkout of the 11 projects from CVS. Then I went to PDE > Target Env and configured the rest of the plug-ins. ReBuild All. Same build problems. Build problems Errors during build. org.apache.xerces.parsers.DOMBuilderImpl: method setFeature (Ljava/lang/String;Z)V not found org.apache.xerces.parsers.DOMBuilderImpl: method setFeature (Ljava/lang/String;Z)V not found org.apache.xerces.parsers.DOMBuilderImpl: method setFeature (Ljava/lang/String;Z)V not found java.lang.NullPointerException encountered while running org.eclipse.pde.internal.builders.ExtensionPointSchemaBuilder. org.apache.xerces.parsers.DOMBuilderImpl: method setFeature (Ljava/lang/String;Z)V not found org.apache.xerces.parsers.DOMBuilderImpl: method setFeature (Ljava/lang/String;Z)V not found java.lang.NullPointerException encountered while running org.eclipse.pde.internal.builders.ExtensionPointSchemaBuilder. org.apache.xerces.parsers.DOMBuilderImpl: method setFeature (Ljava/lang/String;Z)V not found org.apache.xerces.parsers.DOMBuilderImpl: method setFeature (Ljava/lang/String;Z)V not found
This reminds me of the similar (unrelated) errors that were caused by the wrong Xerces somewhere on the classpath. May have nothing to do with this though.
True, we see defects like this one when there is another xerces on the classpath that is masking the one shipped with Eclipse.
This kind of simple PDE usage scenario should be covered by automated test suites run with each build.
The same scenario fails in the same way in Eclipse 2.1.0 (I did not try 2.1.1)! Can you verify this?
I was running I20030618 and 2.1 with ibm-sdk-n141p-win32-x86. When I switched to running 2.1 with ibm-jre-n131p-win32-x86, I no longer see the Build problems.
I think that one of the JDK 1.4.1 started bundling Xerces (and apparently the wrong version as far as Eclipse is concerned :-).
Lowering severity... The choice of a level 1.4 JDK is becoming a problem, as some are bundling xerces which is masking the xerces shipped with Eclipse. This is a product issue rather than a PDE bug.
Moving to Platform Core...
*** Bug 38733 has been marked as a duplicate of this bug. ***
*** Bug 39277 has been marked as a duplicate of this bug. ***
*** Bug 40941 has been marked as a duplicate of this bug. ***
A question: I noticed that Xerces is hard coded as XML parser into Eclipse. As far as I could see, the reason was the use of Xerces specific features to get extended information on the location of XML elements. In my opinion the best approach would be to sit solely on top of JAXP 1.1. In the particular case I've seen (Bug 40941) this is definitely possible. (See for example the DOM parser in JaxMe 2, http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/jaxme/JaxMe2/src/net/sf/jaxme/generator/util/DOMBuilder.java that is used to attach location info to a DOM tree.) Perhaps a similar approach works in other cases too?
*** Bug 43022 has been marked as a duplicate of this bug. ***
*** Bug 43860 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 37696 ***
workaround for this problem: rename xml.jar to xml.jar.old in jre/lib This works fine if you don't need the xml parser in other Java application.
