I didn't track xalan-dev (or my inbox will explode with all the jakartas I follow :), that's why I send that to Shane (sorry)
if someone has a reply thanks to send me a note in direct ;) - Henri Gomez ___[_]____ EMAIL : [EMAIL PROTECTED] (. .) PGP KEY : 697ECEDD ...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 >-----Original Message----- >From: Shane Curcuru/CAM/Lotus [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, June 26, 2002 3:22 PM >To: [EMAIL PROTECTED] >Cc: GOMEZ Henri >Subject: Fwd: JLex 1.2.5 and xalan 2.3.1 > > >Although I hate to say it to someone who's so helpful, this is >a question >best answered on the xalan-dev list. (Especially since I'm not really >running builds anymore) > >XSLTC-folks: have you done any work to see if you can use >newer versions of >JLex as Henri asks below? This might help out his repackaging >work as well >as letting our GUMP runs use newer JLexes etc. > >Oh, and [PATCH] below applied in build.xml 1.174 - thanks! > > - Shane > >----- you "GOMEZ Henri" <[EMAIL PROTECTED]> wrote ----- >Hi Shane, > >Sorry to disturb you but while packaging >xalan-j2 2.3.1 for jpackage project, >www.jpackage.org, i noticed that >xalan 2.3.1 (xsltc) couldn't be built against >JLex 1.2.5. > >Did you have informations about it ? > >BTW, here is a small patch for docs.classpath : > >--- build.xml.orig Wed Jun 26 11:01:07 2002 >+++ build.xml Wed Jun 26 11:00:55 2002 >@@ -155,6 +155,8 @@ > <pathelement location="${xmlapis.jar}" /> > <pathelement location="${parser.jar}" /> > <pathelement location="${bsf.jar}" /> >+ <pathelement location="${bcel.jar}" /> >+ <pathelement location="${runtime.jar}" /> > <pathelement location="${stylebook.jar}" /> > <pathelement location="${doclet.jar}" /> > <pathelement location="${build.xalan.jar}" /> > >Regards > >- >Henri Gomez ___[_]____ >EMAIL : [EMAIL PROTECTED] (. .) >PGP KEY : 697ECEDD ...oOOo..(_)..oOOo... >PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 > > > >
