Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 445156

Summary: sci-geosciences/josm-5485: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Product: Gentoo Linux Reporter: Martin von Gagern <Martin.vGagern>
Component: Current packagesAssignee: Hanno Böck <hanno>
Status: RESOLVED FIXED    
Severity: normal CC: sci-geosciences
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge --info

Description Martin von Gagern 2012-11-29 08:00:16 UTC
Created attachment 330896 [details]
emerge --info

Traceback (most recent call last):
  File "/usr/lib64/javatoolkit/bin/build-xml-rewrite", line 23, in <module>
    tree = et.ElementTree(file=file)
  File "/usr/share/jython-2.5/Lib/xml/etree/ElementTree.py", line 546, in __init__
    self.parse(file)
  File "/usr/share/jython-2.5/Lib/xml/etree/ElementTree.py", line 583, in parse
    parser = XMLTreeBuilder()
  File "/usr/share/jython-2.5/Lib/xml/etree/ElementTree.py", line 1133, in __init__
    self._parser = parser = expat.ParserCreate(None, "}")
  File "/usr/share/jython-2.5/Lib/xml/parsers/expat.py", line 59, in ParserCreate
    return XMLParser(encoding, namespace_separator)
  File "/usr/share/jython-2.5/Lib/xml/parsers/expat.py", line 91, in __init__
    self._reader = XMLReaderFactory.createXMLReader(_xerces_parser_name)
java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser
        at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:229)
        at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:220)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:616)

org.xml.sax.SAXException: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser
 * ERROR: sci-geosciences/josm-5485 failed (configure phase):
 *   build-xml-rewrite failed
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_configure
 *   environment, line 4042:  Called java-ant-2_src_configure
 *   environment, line 1792:  Called java-ant_bsfix
 *   environment, line 1814:  Called java-ant_bsfix_files './styles_nodist/potlatch2/build.xml' './build.xml'
 *   environment, line 1851:  Called die
 * The specific snippet of code:
 *               ${rewriter4} ${gcp} ${enc} -c "${JAVA_PKG_BSFIX_SOURCE_TAGS}" source ${want_source} -c "${JAVA_PKG_BSFIX_TARGET_TAGS}" target ${want_target} "${@}" || die "build-xml-rewrite failed";
 *
 * If you need support, post the output of `emerge --info '=sci-geosciences/josm-5485'`,
 * the complete build log and the output of `emerge -pqv '=sci-geosciences/josm-5485'`.
!!! When you file a bug report, please include the following information:
GENTOO_VM=icedtea-6  CLASSPATH="" JAVA_HOME="/usr/lib64/icedtea6"
JAVACFLAGS="-source 1.6 -target 1.6" COMPILER=""
and of course, the output of emerge --info
 * The complete build log is located at '/var/log/portage/sci-geosciences:josm-5485:20121129-073519.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/sci-geosciences/josm-5485/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sci-geosciences/josm-5485/temp/environment'.  
 * Working directory: '/var/tmp/portage/sci-geosciences/josm-5485/work/josm'
 * S: '/var/tmp/portage/sci-geosciences/josm-5485/work/josm'
Comment 1 Hanno Böck gentoo-dev 2013-01-13 12:57:59 UTC
can you re-check with the latest version 5608?
Comment 2 Martin von Gagern 2013-01-17 22:06:49 UTC
Sorry for the late reply (and thanks for prodding me via chat). 5608 just emerged without errors, but even 5485 will now configure without problems. Not sure where this issue came from, but apparently some factor outside the ebuild contributed to the observed behaviour.

Let me know if someone else experiences this, and I'll reopen the report.