This is a (very) belated reply to Rob's remarks but hopefully he or
others will still be able to help (Sorry, I got sidetracked on other
things for a while).
On 2011-11-01 07:52, Rob Seegel wrote:
Just to be sure I understand here... you have one or more source files
where some of the va
Thanks a lot Stefan.
Exactly, I've trusted the Java API call code written by a coworker of
mine, but when I told him to check it twice he found he set the
basedir wrong. It happens in teamworking...
Thanks once again,
Jo
On Thu, Nov 17, 2011 at 12:45 PM, Stefan Bodewig wrote:
> On 2011-11-17, J
On 2011-11-17, Jo Support wrote:
> 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 l
On 2011-11-14, Knuplesch, Juergen wrote:
> I use OpenSuse 11.4 32 Bit
> I use Java 1.6.0.17, JDK from Sun
> Before that I tried 1.6.022 and OpenJDK.
And you are sure this is what Ant uses?
> The problem I have is when I use the fork attribute.
> Do I have to tell Linux to take the old classpath
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 versi
