Hi,
Ahh,
As I did a lot of work on this more than year ago and haven't touched it since I will give what I can, but it may be wrong.
1. You can build AW yourself and include the most recent version of ANTLR that has the fix. Make sure the most recent version of ANTLR doesn't have the bug before you build it in.
2. You can also bring up AW in NetBeans under the debugger and fix the bug yourself.
3. Search
http://antlr.markmail.org/ for info on the problem, I may have posted a work around, but can't remember. It would be a change to the grammar and not ANTLRWorks.
4. You can try earlier versions of AW as each one will have the version of ANTLR in it at the time was built. You may get lucky and find a version that doesn't have the bug but is recent enough so that you don't lose all of the functionality.
5. If I remember correctly AW does not do the conflict analysis, ANTLR does it and it can be reported using a command line option, can't remember which one. AW is just really good at making it clear visually, which I agree is a great reason to use AW. You might be able to pull that part of the code out of AW and make a stand alone tool.
6. You can get a picture of the parse tree or without using AW. The command line can output a dot file that can then be viewed graphically with a dot viewer. e.g. zgrviewer.
In short, most of the heavy lifting of what you want is done in the command line tool, AW just takes the hard to read output and converts it nicely into a graphical display.
Regards, Eric