Thanks for that pointer, I guess I will use that solution for now. After
following this thread and doing the exec tests, I think I know what would be
needed to solve this for my own (selfish) needs.
The <ant> task would need to have a fork attribute, allowing the new build
file to be called in a new JVM, which would be started up in the new
location.
Two questions following that:
1 - Is that likely to be a difficult task?
2 - Would submissions adding that attribute be appreciated?
With those words I sign off on this thread, since it seems to me that any
further discussion would have to take place on the ant-dev list.
Cheers,
Magnus
> -----Original Message-----
> From: Jason Rogers [mailto:[EMAIL PROTECTED]]
> Sent: 25. september 2001 16:11
> To: '[EMAIL PROTECTED]'
> Subject: RE: stopping an <exec> - <exec> vs. <ant>
>
>
>
> > 1 - Using an <exec> task to run an executable in the bin
> > directory,
> > presumably because the exe-file is not found.
>
> If it's on your PATH, it should be found.
>
> > 2 - Using a System.loadLibrary() call inside my test
> > code, presumably
> > because the dll-file is not found.
>
> If it's on your CLASSPATH or LIBPATH, it should be found.
>
> -Jason
>
