logo       

Re: Moving XMLC to ObjectWeb's SF: msg#00070

java.enhydra.xmlc

Subject: Re: Moving XMLC to ObjectWeb's SF

On Monday 27 January 2003 15:46, Jacob Kjome wrote:
> I have no problem with the move. Sounds like a good idea. However, I'm
> wondering if we shouldn't make a release of XMLC in its current state
> before doing the package renaming? That is, unless it really isn't a big
> deal to do.

Renmaming the packages should not be a big deal - basically, just a
search-and-replace over the import statements in the XMLC sources, without
introducing any new code.

> BTW, does the package renaming include gnu-regexp and jtidy? I'd think
> that would be unnecessary.

gnu.regexp: definitely not. The version included in the XMLC source tree is
the unchanged official version, and XMLC uses only the published API, meaning
it should work with either the offcial version or the one provided by XMLC.

jTidy: Don't know. There are a few patches to jTidy, but jTidy is (as opposed
to Xerces) usually not part of an application server or other "environment"
stuff, so it's much less likely to cause conflicts.

> Xerces is the source of all the problems. The other libraries can be left
> alone until such time as they are deemed to be problematic as well.

Agreed.

--
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


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise