cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Gallardo" <>
Subject Re: [IMP] building Xalan (was: DO NOT REPLY [Bug 28032])
Date Thu, 01 Apr 2004 12:47:52 GMT
Joerg Heinicke dijo:
> Antonio Gallardo <agallardo <at>> writes:
>> > Therefore I recommended to use target "unbundledjar" as this builds a
>> clean
>> > jar. Unfortunately this breaks XSLTC as Java CUP Runtime classes are
>> missing.
>> > Now we can add this JAR
>> (
>> > ourselves or modify the Xalan build system locally: There is a target
>> > "xsltc.copy-deps-jars" where I uncommented the antcall to target
>> > "xsltc.copy-deps-jar" for bcel and regexp.
>> > This jar is now working for me. I will commit it.
>> Great work! I think we can request a new target: "unbundled just Apache
>> libs" to the Xalan project.
>> WDYT?
> I would not like it as part of Xalan community. At the moment there are 3
> jars
> to be included or not. At the end you can provide 2^3=8 targets for all
> different combinations of include the one or the other or not. IMO that's
> overcharged.

I think there can be far more posible combinations since there are more
than 2 version for each jar. But this is OT.

> Therefore I only asked for
> - either "build unbundledjar" + adding java-cup.jar to our CVS

-1 As you posted it encrease the complexity without any valid reason.

> - or "build jar" + removing the bcel and regexp stuff out of it (pre:
> modify
> build.xml, post: remove bcel/regexp by hand after the jar has been
> created)

This is good, because we uses the Apache jars in other blocks (not only in
xalan) and by unbundled it from xalan we can choose the version we need.

BTW, inside the last posted xalan.jar there are still 4 files:


Also inside the META-INF/MANIFEST.MF there is the info about this 2
removed Apache libs too. IMHO this is not too important, but will be fine
to end the job. ;-)


Best Regards,

Antonio Gallardo

View raw message