sbt-antlr4
sbt-antlr4 copied to clipboard
ihji
Antlr4 plugin for sbt 1.1+ and 0.13.x
I'm using a CI environment where the java binary isn't in the path, so `Process("java", args)` throws an exception, so it's really useful to add an option to set an...
I'd like to test the generated parser using grun aka `org.antlr.v4.gui.TestRig`. Amongst other things it provides a simple GUI:  This is probably trivial to do if the example...
I have setup my sbt file as described in the readme. However, when I do `sbt clean compile` I get the following output. Please note that I don't see anywhere...
It looks to me like adding the antlr specific sources to sbt's `managedSourceDirectories` (https://github.com/ihji/sbt-antlr4/blob/3d36e6c/src/main/scala/com/simplytyped/Antlr4Plugin.scala#L80) isn't a good idea, since sbt already has the root directory `src_managed` in the classpath (tested...
The `src_managed` folder should by default adhere to the `main/language/package` convention. Generated sources are Java code, so they should end up in `src_managed/java/package`. This especially fixes source duplication bugs in...
Instead of specify package name parameter, infer the package name from the file path, as `src/main/antlr4/org/sample/grammar.g4` generates package name `org.sample`
Long story short, until very recently, SBT published plugins in a way that was non-standard enough that it made them impossible to retrieve from corporate tooling. The details are a...
Working on a project where I need to run antlr against the same grammar in 2 different sub-projects, 1 being a normal scala project the other being a scala.js project....
