Stephane Bailliez wrote:
>
> Eric,
>
> 1) Pay attention when you are forking a java task that requires an url as a
> parameter.
> The urls always have to be absolute because you never know where will be
> located your vm and the resolution of a relative path may depends on the
> strategy of you
Conor MacNeill wrote:
>
> > From: Eric Richardson [mailto:[EMAIL PROTECTED]]
> >
> > BTW, it would be nice if embedding ant was considered as a design
> > criteria in the next major release. Ant seems to work very well if run
> > standalone or from a script but running from Java is tough at least
> From: Eric Richardson [mailto:[EMAIL PROTECTED]]
>
> BTW, it would be nice if embedding ant was considered as a design
> criteria in the next major release. Ant seems to work very well if run
> standalone or from a script but running from Java is tough at least as
> far as I've tried so far(Alth
Stefan Bodewig wrote:
>
> On Wed, 25 Jul 2001, Eric Richardson <[EMAIL PROTECTED]>
> wrote:
>
> Two notes upfront:
>
> (1) If your replace parser.jar with crimson.jar and jaxp.jar with the
> version of JAXP 1.1, I think xalan2 should work without forking (I may
> be wrong).
Since I'm combining
Eric,
1) Pay attention when you are forking a java task that requires an url as a
parameter.
The urls always have to be absolute because you never know where will be
located your vm and the resolution of a relative path may depends on the
strategy of you java app.
Best thing is to always use the
On Wed, 25 Jul 2001, Eric Richardson <[EMAIL PROTECTED]>
wrote:
Two notes upfront:
(1) If your replace parser.jar with crimson.jar and jaxp.jar with the
version of JAXP 1.1, I think xalan2 should work without forking (I may
be wrong).
(2) Why don't you use the
