The reason I don't want to do this with Tritonus is because we don't have a very good track record of following upstream sources. We currently only have GNU JAXP as external library shipped with GNU Classpath, and we are horribly out of date (libgcj is even more out of date), so I am actually thinking of dropping it and point people to the official GNU JAXP upstream sources.
If JAXP, Tritonus etc can be used out of the box with Classpath, would it be possible to make the Classpath build process simply grab the latest released version from their respective CVS repositories, or something?
It seems a shame to just have to say "Classpath out of the box is incomplete, go get these other libraries too before you have a complete Java environment".
We could make them "dependencies" of classpath, but then you end up with some weird inverted dependency relationships where the other packages require classpath to build, but classpath is marked as requiring the other packages.
Stuart.
-- Stuart Ballard, Senior Web Developer NetReach, Inc. (215) 283-2300, ext. 126 http://www.netreach.com/
_______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
