Sam Ruby wrote:
>
> Glenn Nielsen wrote:
> >
> > The question isn't whether I have upgraded to xalan2 for use with tools
> > like Ant 1.3 (I already use Xalan 2). The problem GUMP had is with the
> > dependency in the java source for the xtags tag library which currently
> > requires the xalan 1.x API. (I am not the author of the xtags taglib, I
> > just do the nightly build) To satisfy those dependencies it has the
> > version of xalan it needs checked in to CVS and its ant build.xml adds
> > that xalan to the ant classpath. I have not been able to reproduce the
> > build failure that GUMP had with the xtags taglib. I tried the build w/o
> > any xalan jar in my shell CLASSPATH, with only xalan1.jar in my CLASSPATH,
> > with only xalan2.jar in my CLASSPATH, and with both in my CLASSPATH.
> > xtags built just fine in all cases. My build uses the Ant 1.3 release.
> >
> > I don't know what caused GUMP to fail when building xtags. But whatever
> > caused it, it isn't a problem in the jakarta-taglibs build.
>
> Gump does not use the jars checked into CVS. Instead, it uses the latest
> versions of the respective dependencies. In the case where there is a
> major version (Xerces 1&2, Xalan 1&2, Tomcat 3&4), I will generally build
> both for a period of time.
>
> For Xalan 1, that period is over.
>
What is GUMP, and what service does it provide for the jakarta-taglibs project?
GUMP does a verification that jakarta projects build, but doesn't honor their
API version dependencies? Isn't that a bit draconian? Is this something
you decided, or is this a position of the Jakarta PMC?
> If you wish to reproduce this failure, simply specify
> -Dbuild.sysclasspath=only on your invocation of ant.
>
Now that I know that GUMP doesn't honor the jakarta-taglibs API build
dependencies, there is no need.
> IMHO, intentionally staying downstream in your dependencies does a
> significant disservice to the Jakarta and xml.apache.org communities.
>
> - Sam Ruby
Thats fine, I have no argument with that.
Perhaps verifying that jakarta projects build and policing use of deprecated
API's should be separate things.
Posting a long GUMP build failure to tablibs-dev every day due to GUMP not
honoring API dependicies doesn't solve anything, and when it fails doesn't
finish verifying the normal jakarta-taglibs build process.
(Not the author of jakarta-taglibs/xtags)
Regards,
Glenn
----------------------------------------------------------------------
Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder |
MOREnet System Programming | * if iz ina coment. |
Missouri Research and Education Network | */ |
----------------------------------------------------------------------
