Bugzilla Bug 113601

This is the first patch in a series targeted against axxo overlay.
It adds the xml-commons-1.0_beta3, which contains an important update
to the xml-apis.jar. Namely, JAXP 1.3 classes.

Actually, this is an ebuild proposal. I'll post it as a patch against
existing xml-commons-1.0_beta2.ebuild

Things to note:
* This ebuild is based on the version checked out from the Apache SVN.
  See the URL that demonstrates the problem for the origin.

* Consider this package experimental. But the previous version is dated
  Feb 2002, so it was the high time it was bumped. JAXP 1.3 classes
  are required for newer xalan-2.7.0, so this package is badly needed.

* I've cleaned the source code of this "release" and I've put it on my
  home page. This is reflected in the .ebuild file with two SRC_URI
  entries - the first one commented out, and a second one pointing to
  my site. This is temporary workaround and can be removed at a request.

* I tested it currently only on ~x86 and it is keyworded as such
  (I can test it under ~amd64 in several days)

* I don't have currently jikes installed, so I haven't tested this ebuild
  against USE="jikes" flag. I just copied the existing logic from 1.0_beta2.

* I tested it against the following USE flags:
  "doc source", "doc -source", "-doc source", "-doc -source"

* The package after installation produces three .jar files:
  - xml-apis.jar (the most important)
  - which.jar
  - resolver.jar

* The last JAR is a bit problematic (I think), because similar file is
  installed by the xml-commons-resolver-1.1 package. I'd like to hear
  opinion(s) on how to deal with this. BTW. separate resolver distribution
  can be built using the same sources - quoting the "readme-build.txt":

Step 2
------
cd xml-commons/java
ant -buildfile resolver.xml dist
... Builds separate resolver distribution and copies over some relevant
Forrest-built docs.

  So probably the xml-commons-resolver could be also enhanced if required.

* The Apache team will probably release the final xml-commons-1.0, based
  on some Forrest tool. This is not needed right now, bu may be in the future.
  Just to notify interested people.


Reproducible: Always
Steps to Reproduce:

Created an attachment (id=73616) [details]
xml-commons-1.0_beta2.ebuild.patch

The patch against current dev-java/xml-commons-1.0_beta2.ebuild

Created an attachment (id=73617) [details]
1.0_beta3-jdk15-n-javadocs.patch

A patch needed for xml-commons-1.0_beta3.ebuild.
Fixes three ant's xml files for the right sources, javadocs, and classes.

When you do a CVS/SVN snapshot, it is a generally a good idea to include info
about how it was checked out. For SVN living on http, it should be suffice to
include a URL.

(In reply to comment #3)
> When you do a CVS/SVN snapshot, it is a generally a good idea to include
> info about how it was checked out.

Ok, I'll remember that.

> For SVN living on http, it should be suffice to include a URL.

It was a trunk build, because tagged verions only include
xml-commons-1_0_b1 and xml-commons-1_0_b2.

So, the URL used was:
http://svn.apache.org/repos/asf/xml/commons/trunk/

You can find the tarball of this checkout on my webpage:
http://ics.p.lodz.pl/~wiktorw/gentoo/distfiles/xml-commons-1.0.b3.tar.gz

This is essentially the checkout done on 17 Nov 2005, excluding:
* all .svn directories
* all .cvsignore files
* xalan-src.zip and xml-xerces.zip files from contrib/jaxp13/ directory

I did a diff on the "old" and the current revision (05 Dec 2005, rev. 354051)
and the differences are minimal. There is only one file different,
java/src/org/apache/xml/resolver/apps/XParseError.java and the changes
are only for error and warning counts. (see attached diff)

Created an attachment (id=74090) [details]
trunk-20051205.diff

A diff between the previous trunk checkout (17 Nov 2005) and current
(05 Dec 2005, revision 354051).

From what I can gather, the new xalan and xerces need the new JAXP API,  
provided by this package. 
 
Also, contact has been made with the xml-commons team, and with any luck, they 
will make a new release of xml-commons. 

I've added dev-java/xml-commons-external to portage. Upstream xml-commons is  
actually divided into a few components. This is one of them, which is the 
external XML libraries, ie things provided by W3C. and provides xml-apis.jar. I 
also believe it provides the JAXP 1.3 classes, as I'm able to build xalan-2.7.0 
with it. 
 
As for xml-commons, I believe it's best to wait till an official upstream 
release, or in the very least till they make a tag in version control for it. 
 
Because xml-commons-external provides the classes we need for xalan and xerces, 
I'm going to mark this as fixed. 

(In reply to comment #6)

> Also, contact has been made with the xml-commons team, and with any luck, they 
> will make a new release of xml-commons. 

Great, it's been years since they released 1.0_beta2 ...
Good job :-)