some more digging:
The importVocab statemtn cannot be used if referencing grammar with package declaration. possible solution:
1. the generated source must be generated in an order that respects `importVocab` dependencies in the grammar.
2. gradle should pass the output directory of a grammar file as -lib folder to allow referencing grammar from same package that has been generated before
As it currently stands I think Gradle has 0 support for using packages with separated lexer and parser files, since passing in `-lib` and `package` myself does nothing. I'd like to be able to put my grammars in a package, but that seems to be impossible as it currently stands.
In the meantime, is there at least any workaround for this? It stinks to have to stick with 2.4 to get working Antlr 4 support.
@Rene, I do not use importVocab (just tokenVocab in the parser) with the Antlr 4 grammars. So the issue is not limited to that
@Kenzie, fwiw I use split lexer and parser design with packages and it "works".. so long as you stick to Gradle 2.4. In my experience I have not been able to move past 2.4 or it breaks.
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.
We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.
Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
- Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
- Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!
I still "advocate" for a total revamp of the Antlr plugin. It really does not handle different Antlr versions well (or really at all).
@Steve Thank you. Would you be willing to contribute to such a "revamp" if it began?
I have already...
- https://github.com/hibernate/hibernate-semantic-query/blob/master/build.gradle#L159
- https://discuss.gradle.org/t/gradle-3-and-antlr/18514/11
- not to mention that I helped with the original Antlr (v2) support in Gradle
My plugin (1st link) has some poor design points in the sake of ease-of-use in Hibernate, which is what I needed this for.
A more generally useful plugin/task for Antlr v4 (and v3 I believe) would perform discovery and actually inspect the grammar files to figure out things like generation-order, package names and corresponding directory structure, etc. Antlr uses itself at runtime to parse these grammar files; you can manually perform all these steps yourself which gives you access to valuable information.
I can help some with that. I might be beneficial to reach out the Antlr team and see if they are willing to take over that plugin. Contribution is how they started supporting the Maven plugin.
Of course — I didn't mean that you haven't contributed already
Thank you for the suggestion.
I just mean that discussion and that plugin are a good start on specifically Antlr v4 that actually works between Gradle 2 and 3.
I know compat with older versions of Gradle is not the top priority of the Gradle team, but it is an amazing thing when it happens to happen with no extra work
As I said on the forum thread (2nd link) I personally think this needs specific plugins/tasks for each version of Antlr. But honestly that's the same thing I suggested when it was decided to fold Antlr v3 support into the same v2-based plugin. The plugin I wrote for Hibernate would not work at all against versions of Antlr prior to v4.
Moved to https://github.com/gradle/gradle/issues/1240 — I expect that we will reach out to the Antlr team for their help soon.