Cool. Thanks Richard! Your changes work well and I modified the example
apps to account for them.
Enhydra team: does this work for you? All you will require from
release/lib is xmlc.jar (or xmlc-base.jar and xmlc-xerces.jar), xhtml.jar,
wireless.jar, jtidy.jar, gnu-regexp.jar, and bcel.jar. And then, of
course, xercesImpl.jar and xml-apis.jar from the latest Xerces2 (2.4.0
currently).
Now we need to address whether failures in the testcases should stall an
XMLC-2.2 release or whether they can be ignored (maybe the testcases are
obsolete???) and just release XMLC-2.2 as is. Are there any other mods
that are needed? Again, ideally, I would like someone to look over
OutputOptions and verify that the javadoc is correct and that the defaults
there are appropriate before an XMLC-2.2 release.
Jake
At 07:45 PM 7/9/2003 +0200, you wrote:
On Wednesday 09 July 2003 19:10, Jacob Kjome wrote:
> Would xmlc-base.jar and xmlc-xerces.jar still exist as well after xmlc.jar
> is generated, or are you saying those would be deleted?
They stay in release/lib - removing them would mean more changes to the build
process (e.g. for dependency checks)
> Also, I assume that the xmlc.jar would be generated by default
> where the target that creates the xmlc-all-runtime.jar is
> optional. Actually, maybe you can hook things up so that
> xmlc-all-runtime.jar also gets created by default?
Done :-)
> Anyway, I'll have to make a mod to the example app builds after you commit
> this, so if you can drop me a note when you are done doing the commit, it
> would be appreciated.
It's in CVS now.
--
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
| 