removed `./java/external/build/xml-apis.jar' !!! ERROR: dev-java/xml-commons-1.0_beta2-r1 failed. Call stack: ebuild.sh, line 1615: Called dyn_install ebuild.sh, line 1061: Called qa_call 'src_install' ebuild.sh, line 44: Called src_install xml-commons-1.0_beta2-r1.ebuild, line 50: Called java-pkg_dojar 'java/external/build/xml-apis.jar' java-utils-2.eclass, line 282: Called die !!! java/external/build/xml-apis.jar does not exist !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/dev-java/xml-commons-1.0_beta2-r1/temp/build.log'. So we are installing this bundled jar. There are also lots of other bundled things in there. In java/external there are links to where the jars come from so we should be packaging them separately and make packages depend directly on the needed stuff.
Later releases of xml-commons are split into xml-commons-resolver and xml-commons-external. The jar missing here is part of the latter. I suggest we tree clean xml-commons if possible. dev-db/jxtray and www-servers/axis are the only reverse dependencies both which are dead as well as the only consumer of axis, namely dev.java/mx4j which is super seeded with jsr160 in java 5 and java 6 and hasn't seen an update since 2006. Nothing depends on mx4j but gnu-java-mail blocks it ;) If there really is a point to keep any of those packages using xml-commons-{resolver,external} could be made to work. @java: any comments?
It's been dealt with a while ago in 58b7977b06dabd979ac4fec5d15832dd85fa678d and doesn't use bundled jars anymore. Closing.
