You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my case, I was trying to look at the source for AbstractParseTreeVisitor. My workaround was to get the source for antlr4-runtime artifact and substitute it for the antlr4 source in the Eclipse build path. If I ever need to look at the Antlr source for parsing or lexing, I'll be scratching my head for days trying to figure out what's wrong.
Interesting. @parrt I don't think this particular artifact is supposed to include the runtime classes either. It looks like the shaded jar got uploaded to Maven central instead of the original artifact. The shaded jar was only created for non-Maven based distributions.
@cowang I think the source for runtime and the tool should be in separate jars and then the various IDEs will pull it in. antlr4 is the tool and antlr4-runtime are the mvn artifacts. The shaded jar should not have been deployed.
The source artifact for
does not contain sources for the (contained) antr4-runtime.
Dependent on the order of the classpath (read maven-imports) this prevents eclipse from showing javadoc/source for the runtime-classes.
Please include all sources in the source artifact for antlr4.
The text was updated successfully, but these errors were encountered: