At 04:47 PM 7/9/2003 +0200, you wrote:
On Wednesday 09 July 2003 15:53, Jacob Kjome wrote:
> Sounds reasonable to me. If there aren't objections from other XMLC
> developers today, then I'll make the change. Is the name xmlcxml.jar
> acceptable to everyone? Any other suggestions?
Hmmm - XMLC absolutely depends on its own patched version of Xerces, and I
can't think of any reason why anyone wants to use a patched, old version of
Xerces under the org.enhydra.apache.* namespace independent of XMLC.
So, why not simply merge xerces.jar into xmlc.jar for the release?
That's not a bad idea either except that it is a separate module and the
simplest thing to do is leave it separate for now. Actually, the
xmlc-all-runtime.jar was meant to be the solution to the separate jar issue
and since it performs all its work after everything has been built, it
doesn't affect any of the individual modules. The Enhydra guys don't seem
to want to use the all-in-one jar file, though. I'd go with the suggested
change to the xmlcxml.jar as the simplest solution. Besides, future
versions of XMLC will probably use a different xml implementation so moving
things too close together might not be the best thing to do.
If you have a solution that you feel is clean and simple to implement in
the XMLC build, then maybe you can articulate that and/or commit it to
CVS. For the moment, I am willing only to do the work of modifying the
name of the xerces.jar to xmlcxml.jar.
Jake
--
Richard Kunze
[ t]ivano Software, Bahnhofstr. 18, 63263 Neu-Isenburg
Tel.: +49 6102 80 99 07 - 0, Fax.: +49 6102 80 99 07 - 1
http://www.tivano.de, kunze@xxxxxxxxx
| 