<dependency>
<groupId>org.antlr</groupId>
<artifactId>antlr4-runtime</artifactId>
<version>4.5.3</version>
</dependency>
You only need the runtime jar for generated code. As you are probably aware, for the ANTLR tool you need:
<plugin>
<groupId>org.antlr</groupId>
<artifactId>antlr4-maven-plugin</artifactId>
<version>4.5</version>
<executions>
<execution>
<goals>
<goal>antlr4</goal>
</goals>
</execution>
</executions>
</plugin>
Jim
--
You received this message because you are subscribed to the Google Groups "antlr-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to antlr-discussi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Actually the issue is that I need the source for the runtime to be present in the sources jar. For source lookup by the IDE.
Yes, well understood and effectively what I am doing. But the runtime jar does not include the tool. And, I need tool source lookup as well.
Having both the binary (and source) tool and runtiime jars in the project is problematic for several reasons. Notably, the binary tool jar includes the runtime, meaning there is a redundant source of class files. Seems Eclipse source lookup can get confused as to the true source jar to use when doing the lookup from a text hyperlink. Happens most frequently when a tool source lookup has just been performed. Could be source lookup is not using a pure classpath resolver.
The other is now my project is setup to ship dual runtimes. Theoretically, not a problem, but not desirable as a practical matter.
Is there some particular reason why the tools source jar should not have a 1:1 correspondence with the contents of the tools binary jar, i.e., also include the runtime source?
Thanks,
Gerald
--