eclipse-xtext / eclipse-xtext/xtext
Update to antlr 3.5.3
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
So even the latest version of xtext uses 16 years old version of antlr-runtime 3.2, which is causing a lot of stress at the moment in my project. I use drools engine v7+ which uses 3.5.2 version of antlr-runtime, and I can't exclude it as it relies on changes it has over 3.2, and xtext doesn't work with 3.5.2 as it crashes with EOF_TOKEN exceptions.
Caused by: java.lang.NoSuchFieldError: EOF_TOKEN
at org.eclipse.xtext.parser.antlr.Lexer.nextToken(Lexer.java:60)
at org.antlr.runtime.BufferedTokenStream.fetch(BufferedTokenStream.java:143)
at org.eclipse.xtext.resource.SynchronizedXtextResourceSet.getResource(SynchronizedXtextResourceSet.java:33)
Is there any particular reason why xtext hasn't progressed with dependency updates, and is it planned to do so any time soon?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the antlr-runtime dependency used by Xtext and the failure at org.eclipse.xtext.parser.antlr.Lexer.nextToken, reproducing the EOF_TOKEN crash alongside Drools Engine 7+. Done means Xtext works with antlr-runtime 3.5.3 without that crash and the relevant compatibility checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100