On a recent Orbit call (the last of
2006), we spent some time discussing the bundling of libraries that are
provided as a multitude of JARs. The particular example was Batik,
which I am contributing under https://bugs.eclipse.org/bugs/show_bug.cgi?id=166207.
With the help of my colleagues on the call, I came away convinced
that the best approach to bundling Batik's 16 JARs would be to follow the
same strategy as GMF had implemented already: one bundle containing
the individual OEM JARs within it, unpacked on installation, with the exception
of the org.w3c.* packages from the batik-ext.jar which would be bundled
(the latter three bundles not having
The problem now is, that the Java language
bindings for the W3C standards that these latter three bundles would comprise
are only available from w3c.org as ZIPs of *.java files. They aren't
versioned, so I would have to assume that they only have one version (the
specification's version, which is 1.1), and that Batik compiled these same
source files for their distro.
So, I am inclined to just contribute
GMF's org.apache.batik bundle to Orbit as is (basically, just copy the
project from GMF's CVS module to the Orbit module). For the purpose
of package exports, most packages will have the "1.6" version
number, and for the org.w3c packages I'll just have to use the current
W3C specification number.