Hmm, I don't know what could be the cause of the poor performance. I've
never used ANTLR 3 much tbh. As for the task name, it is indeed defined by
the name attribute of the taskdef, but note that in your current working
example, you are using your own taskdef and are effectively bypassing the
antli
Hi Matt,
thanks: one step further!
I tried now
...
It seems to create parsers only when grammar changed, so it is ok, but:
it is very slow: 11 secs if no parser is created and 30 if grammars are
created.
So a large portion of ti
See inline for some commentary:
On Mon, Aug 19, 2013 at 2:28 AM, Ernst Reissner wrote:
> Ok, got one step further:
> now i have:
>
>
>
>
>
>
>
>
Here you define the task as being named "ant-antlr3":
> classname="org.apache.tools.ant.antlr.ANTLR3"
>
One side note: you are using 1.8.2 (Dec 2010) and I suggest updating to
1.9.1 (Jul 2013).
http://ant.apache.org/faq.html#history
> Ok, got one step further:
> now i have:
>
>
>
>
>
>
>
> classname="org.apache.tools.ant.antlr.ANTLR3"
> classpathref
Ok, got one step further:
now i have:
which seems to work.
But when i try to use the new task by
ant complaints
ernst@localhost:~/Software> ant genParser
Buildfile: /home/ernst/Software/build.xml
init:
genParser:
BUILD FAILED
/home/erns
Hi Jan,
i tried
>name="ant-antlr3"
> classname="org.apache.tools.ant.antlr.ANTLR3"
> />
as you suggested (which looks much better than what i did before).
Result
ernst@localhost:~/Software> ant genParser
Buildfile: /home/ernst/Software/build.xml
BUILD FAILED
/home/ernst/Software/
I downloaded the antlr.zip and had a look.
In the ant-antlr3.jar there is the antlib.xml at your location.
If all classes are present you could try using the taskdef from that antlib
file:
and remove your xmlns declarations.
Jan
> -Ursprüngliche Nachricht-
> Von: Ernst Reissner [mai