4

I'm trying to use ANTLR3 task for Ant, but I get an "Unable to determine generated class" build failure message.

A quick research shows that many people have had the same problem, with no solution provided (see links below).

Can someone suggest a solution that doesn't resort to using a regular Java Ant task?

External links:

polygenelubricants
  • 376,812
  • 128
  • 561
  • 623
  • Not an answer but a comment, since it's just a guess: perhaps an older version of ANTLR is used by ANT? If you do a `ant -diagnostics` on your shell, there should only be `ant-antlr.jar` and `ant-antlr3.jar` under `ANT_HOME/lib jar listing`. If there's also a `antlr2?.jar`, try removing it. – Bart Kiers Jul 29 '11 at 17:54

1 Answers1

1

The antlr task included with Ant 1.8.2 (the latest version) seems to be dependent on ANTLR 2.7.2 (defined in $ANT_HOME/lib/ant-antlr.pom and using $ANT_HOME/lib/ant-antlr.jar.

What the task is doing is scanning the target file for a line matching ^class (.*) extends .*, where the first match group will be used as the name of the generated file. This whole bit of syntax seems to have been dropped in ANTLR 3.x, or at least made optional, because I'm able to generate parsers without it using the regular java task work-around you mentioned.

On the front page of http://antlr.org/ under the "File Sharing" heading is a link to ANTLR v3 task for Ant, but unfortunately it doesn't appear to be the sort of drop-in replacement I was hoping for. Actually, it seems to be rather convoluted so I've stuck with using the plain java task.

Brad Mace
  • 27,194
  • 17
  • 102
  • 148