OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [docbook-apps] ANT script


At 17:04 12/04/2004, Oliver Horn wrote:
>Hi!
>
>Dave Pawson has documented how to use Ant 1.5 with DocBook [1].
>
>Since Ant 1.6 it is possible to use directly the XML catalog resolver 
>library [2,3] from xml-commons.

<grin/> And Oliver is going to update my content for 1.6?


>However, using Ant for XSLT processing causes a lot of classloader 
>problems, in particular if you want to use a specific XSLT processor or 
>some extension libraries.  Have a look at the Ant 1.6 xmlcatalog 
>documentation [3] and the FAQ entry "<style> or <junit> ignores my 
><classpath>" [4]:
>
>a) XML catalog resolver library must be on the (system) classpath
>b) SAXON (or your XSLT processor of choice) must be on the same classpath 
>as the Ant TraX liasion (lib/ant-trax.jar)

Sounds hairy Oliver, is it?

>c) Extension libraries for XSLT processing must be on the same classpath 
>as the XSLT processor
>
>I think the easiest way is to put all those libraries on the system classpath.

Which some people (e.g. me :-) don't like doing, since I need to vary
the classpath frequently.


>However, I use a slight different approach: I've set up a minimal Ant 1.6 
>environment (only ant.jar, ant-nodeps.jar, ant-launcher.jar and 
>resolver.jar on the system classpath) and load all other libraries 
>(ant-trax.jar, SAXON and various DocBook XSL extension jars) at run-time 
>by the Ant buildfile.  This works fine, too.

I.e set the classpath using the same script as the ant callup?

regards DaveP




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]