move swing related stuff out of runtime package into org.antlr.v4.gui

[parrt]

Fixes #576

[parrt]

only issue might be that org.antlr.v4.runtime.misc.TestRig is how you run the command-line grammar tester but now it's org.antlr.v4.gui.TestRig. maybe the answer is to alter the PR so that the package names are absolutely the same but would just be included with a different jar

[sharwell]

only issue might be that org.antlr.v4.runtime.misc.TestRig is how you run the command-line grammar tester but now it's org.antlr.v4.gui.TestRig. maybe the answer is to alter the PR so that the package names are absolutely the same but would just be included with a different jar

I think we have enough confusion surrounding TestRig for beginners already. I think keeping the same exact name is a very good idea.

[parrt]

closing and rebuilding.

[sharwell]

The other option here is doing what you have, but leaving a shim TestRig in the runtime in the same place it is now. The shim TestRig in the runtime would:

1. Attempt to locate the new TestRig in the classpath, and if that fails print a message that the tool jar must now be available if you want to run test rig.
2. If the new TestRig is found, print a message that TestRig has moved and the new one is being called automatically, then call its main() with the same arguments.

📝 Compared to this PR, implementing this option would only require the addition of the shim TestRig class in the runtime library.

[parrt]

interesting. ok, pushing new version that says:

Use of TestRig now requires the use of the tool jar, antlr-4.X-complete.jar
Maven users need group ID org.antlr and artifact ID antlr4

or

Warning: TestRig moved to org.antlr.v4.gui.TestRig; calling automatically

if you have full jar. No warning if org.antlr.v4.gui.TestRig called.

[parrt]

Fixes #576

[sharwell]

👍