Hi Sam
I've ported over the xtags library to the new build process so that now the
JARs in xtags/lib/* have been deleted. This may cause a GUMP failure soon.
After more research I've realised that Xalan 2 ships with a JAR called
xalanj1compat.jar (notice the j after xalan - I missed that the first time).
So now xtags builds off a regular Xalan 2 distribution, its just that both
xalan.jar and xalanj1compat.jar are required to perserve the backwards
compatible tag which supports old xalan 1 (JAXP 1.0) deployments.
Though after the first real release of xtags I'd like to remove the
backwards compatible tag as, if nothing else, it makes the build process
even more complicated than it is already. So this xalanj1compat.jar issue
will hopefully go away in a month or so.
James
----- Original Message -----
From: "Sam Ruby" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, June 30, 2001 12:55 AM
Subject: Re: [GUMP] Build Failure - Taglibs
> Just to prove that I'm not *TOTALLY* inflexible, tonight's Gump run will
> include the xtags/lib/xalan.jar - and *ONLY* that jar - in the classpath.
>
> In a previous note I indicated that "if you can't find a maintainer for
> xtags, it should be removed. If it is maintained, it should not depend on
> things which are out of service."
>
> It is now clear to me that there is a maintainer for xtags, and one who is
> well aware of
> of Xalan2, TRaX, and JAXP 1.1. In fact, it appears that every effort to
> not only support the new interface, but also to maintain some level of
> backwards compatibiltity.
>
> My hats off to you, James.
>
> - Sam Ruby
>
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
