Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Issue with Antlr 3.4

In project Xtext we use (a custom) ANTLR 3.2, which basically has the same issues. We do use antlr-runtime only directly, which is valid and can be found in Orbit. The dependency on antlr 2.7.7 comes from stringtemplate, which is used by the ANTLR generator and by antlr-runtime optionally. This has to be excluded.

Since we do use org.antlr:antlr in Xtext for generating the parser, but we can’t bundle that, Xtext downloads this on demand separately or leaves the (unrecommended) option to use a home baked packrat parser.

This makes the code free from a code/linking dependency of unallowed ANTLR parts.


Am 17.04.2019 um 09:18 schrieb Geyer-Blaumeiser Lars (INST-CSS/BSV-OS3) <lars.geyer-blaumeiser@xxxxxxxxxxxx>:

Hello guys,

We are depending on a component that is using antlr 3.4. But interestingly, with antlr 3.4 comes a compile dependency to antlr 2.7.7, which isn't approved from emo for understandable reasons. How did you resolve the issue in your project when using antlr 3.4? Especially, if it is a transitive dependency that cannot easily be upgraded.

Mit freundlichen Grüßen / Best regards 

Dr. Lars Geyer-Blaumeiser

Bosch Software Innovations GmbH
Customer Success Services - Open Source Services (INST-CSS/BSV-OS)
Stuttgarter Str. 130
71332 Waiblingen

Tel. +49 172 4815079

Connect with us on Twitter <> , LinkedIn <>  and YouTube <> !

Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr. Stefan Ferber, Michael Hahn, Dr. Aleksandar Mitrovic

cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top