Not obviously to me. fork defaults to false in ant 1.7.1, so I would
have expected the same.
On Fri, Jul 3, 2009 at 12:49 PM, clconway wrote:
>
> You are right. fork="true" in the Ant java task works too. But this was not
> necessary in the original Ant build script. Is there an explanation in the
You are right. fork="true" in the Ant java task works too. But this was not
necessary in the original Ant build script. Is there an explanation in the
documentation of why antrun behaves differently?
-Chris
bimargulies wrote:
>
> A simple fork=yes would have done the job.
>
> On Fri, Jul 3,
A simple fork=yes would have done the job.
On Fri, Jul 3, 2009 at 12:01 PM, clconway wrote:
>
> The problem seems to be that Rats! calls System.exit() (or similar),
> terminating the JVM. I would have thought that Ant would wrap this (the java
> task is copied over from a build.xml and it doesn't
The problem seems to be that Rats! calls System.exit() (or similar),
terminating the JVM. I would have thought that Ant would wrap this (the java
task is copied over from a build.xml and it doesn't terminate the Ant
build), but the following works by forcing the Rats! process into a separate
JVM:
Funny story. I tried replacing the Ant task with a Maven plugin, by writing a
RatsMojo class that invokes xtc.parser.Rats directly and replacing the
plugin element above with
edu.nyu.xtc
maven-xtc-plugin
generate-sources
rats
Stephen Connolly-2 wrote:
>
> you need to use buildhelper-maven-plugin to attach the generated-sources
> directory. Maven does not know that you've generated additional sources.
> Most/all of the source generator maven plugins will add the
> generated-sources/pluginname folder as an additional
you need to use buildhelper-maven-plugin to attach the generated-sources
directory. Maven does not know that you've generated additional sources.
Most/all of the source generator maven plugins will add the
generated-sources/pluginname folder as an additional source path...
buildhelper is there to
My project generates source code using the XTC parser generator
(http://cs.nyu.edu/rgrimm/xtc/). XTC doesn't have a Maven plugin that
I'm aware of, so I'm trying to build the parser using an Ant Java
task, like so:
maven-antrun-plugin
generate-sources