Community
Participate
Working Groups
In order to switch from ant1.4.1 to ant1.5, I replaced (ant.jar/jakarta-ant-1.4.1-optional.jar/xmlParserAPIs.jar/xercesImpl.jar) to (ant.jar/optional.jar/xercesImpl.jar/xml-apis.jar). But then, the call to ant by invoking build.xml (Run Ant ...) fails saying "XML parser factory has not been configured correctly: Provider for javax.xml.parsers.SAXParserFactory cannot be found". Looks like, it somehow fails to read the new manifest.mf file. Or remembers the previous file). Also, the Ant-classpath does not persist between two sessions of Eclipse (i.e. when I close the eclipse and come again, the classpath gets reset to ant1.4.1 !?!) - but that is another issue.
Note that the xml-xerces and xml-xalan communities at xml.apache.org might have comments, along with the jakarta-ant community obviously. The Xalan-J project ships the xml-apis.jar file from the xml-commons repository; normally it's used in Xalan builds (where it includes just the xercesImpl.jar from a Xerces-J build). Note that the xml-apis.jar is mostly a superset of the xmlParserAPIs.jar file (which Xerces-J manages), however there may be a few subtle code changes in some files, and the manifests between these two files are not currently coordinated at all (afaik). But that shouldn't matter, since the xercesImpl.jar file should have already definied the proper META-INF/services/... keys that point to it's own SAXParserFactoryImpl, which the JAXP FactoryFinder code should have read and properly gotten the Xerces parser stuff. My first guess would be classloader wierdness in Eclipse, since the JAXP code itself is in xml- apis.jar, but the Xerces services properties and implementations are all in xercesImpl.jar. (Just a guess...)
Created attachment 2063 [details] TRAX only apis
Ant 1.5 works with Eclipse 2.0.1, I also added xalan 2.4.0 and the previously attached trax only apis in external tool classpath. BTW, you should keep xerces_4_0_5 or you broke completly eclipse, something weird with the eclipse classloader ?
*** Bug 25005 has been marked as a duplicate of this bug. ***
With eclipse moving to Ant 1.5.1 (in Head and proposed to be in the integration build of Oct 29th), can someone step up to verify that this bug report is no longer a problem?
Problem still reported (see bug 21809)
Needs investigation
We have come acoss this problem with Eclipse 2.0. We're going to go to the latest 2.1 M3 build as a fix.
Note that the problem seems to be related to using a 1.3.* VM.
Confirmed that the problem does not occur if using a 1.4.* VM Reproduceable on 1.3.1_06.
With the workarounds described, will look at again after 2.1 but likely no fix to be had here.
This was a problem with the Xerces classes being loaded across multiple class loaders. This has been fixed by: setting the thread context classloader all Xerces classes should and can be loader from the plugin classloader for the Xerces plugin provided by Eclipse Xerces is on the bootclasspath for 1.4.* VMs. See bug 33117 and bug 33664 for more details. Closing.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
