I'm not in a position to verify just at the moment, but I don't think
Martin was suggesting you write code so much as showing you the properties
used by the task which should translate into XML attributes.
Matt
On Aug 16, 2013 11:40 AM, "Kerry, Richard" wrote:
> Goodness, I wasn't anticipating n
On 2013-08-14, Kerry, Richard wrote:
> I'm trying to get DocBook WebHelp building working, which uses Ant to
> control the various processes involved, in particular Xslt. I would
> like to use Catalogs for resolving my XSL stylesheet locations, and
> have thus far been unable to make this work.
On 2013-08-15, Jason Bastek wrote:
> Normally I would do this by removing the destfile (whether it's a
> symlink or a regular file) before recreating it. But I'm not seeing a
> nice way to do this with Ant.
There is no built-in way to do it, the dependset approach you showed in
the later part of
Goodness, I wasn't anticipating needing to write code to get this sorted
But, as a C++ programmer, Java looks quite familiar. However, I have no
experience of developing in it.
If this is the way I need to go please can someone point me at some information
on how to get started in order
Richard
the best way to handle this is to turn on full debugging ..here are the
parameters you will want to supply to the taskdef
/** destination directory */
private File destDir = null;
/** where to find the source XML file, default is the project's basedir */
private File
I don't think this covers my use cases, in particular :
1. External catalog file (Catalog.xml).
2. Use of the catalog to find the xsl file for the transform (ie the "style"
attribute or sub-element of ).
Does anyone have an example using these ?
1. I've developed the catalog while
