ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jo Support <jo.supp...@gmail.com>
Subject Weird "xslt" task behavior
Date Thu, 17 Nov 2011 10:04:41 GMT
Hello everybody,

I've noticed a weird behavior from "xslt" task relating to relative
paths. It seems that "xslt" task set the context for the "style"
attribute relative path in two different ways, depending on the way
Ant has been executed (via command line, or via Java API).

Scenario:

Ant version: 1.8.0/1.8.2 (both act the same way)
OS: Windows XP

Directory tree:

/
	antscript/
	stylesheet/
	project/
		filestobetransformed/
			somesubdirswithfilestobetransformedtoo/
			xslttarget/

I assumed that the attribute "basedir" of "xslt" ant task should be
the working dir containing files to be transformed, and the path
written in "style" attribute should be indipendent from the "basedir",
so I wrote:

		<xslt basedir="/project/filestobetransformed/" extension=".xml"
destdir="xslttarget/" style="./../stylesheet/setThisAndThat.xsl">
			<include name="**/pom.xml"/>
		</xslt>

All works fine when I execute the Ant script via command line, but
when Ant is executed via Java API, it seems that the "./" heading the
relative path in "style" attrubute, leads to the "basedir" attribute
value, because I get the following error:

	FAILED: /project/stylesheet/setThisAndThat.xsl doesn't exist.

So, the "./" has been seen as /project/filestobetransformed/ (basedir
attribute value), and no more as the location of the Ant script.

What am I doing wrong?

Thanks a lot in advance,

best regards
Jo

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message