In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

Irrelevant

What is the connector configuration?

Irrelevant

What is the captured database version and mode of depoyment?

(E.g. on-premises, with a specific cloud provider, etc.)

Irrelevant

What behaviour do you expect?

io.debezium.connector.mysql.antlr.MySqlAntlrDdlParser will work properly with upgraded version of antlr4-runtime

What behaviour do you see?

io.debezium.connector.mysql.antlr.MySqlAntlrDdlParser is failing when upgrading package antlr4-runtime. 

Error:
java.lang.NoClassDefFoundError: Could not initialize class io.debezium.ddl.parser.mysql.generated.MySqlLexer java.lang.NoClassDefFoundError
{{}}
{{ The NoClassDefFoundError stacktrace is}}
{{}}
io.debezium.connector.mysql.antlr.MySqlAntlrDdlParser.createNewLexerInstance(MySqlAntlrDdlParser.java:84)
io.debezium.connector.mysql.antlr.MySqlAntlrDdlParser.createNewLexerInstance(MySqlAntlrDdlParser.java:46)
io.debezium.antlr.AntlrDdlParser.parse(AntlrDdlParser.java:67)
 

Do you see the same behaviour using the latest relesead Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

Yes, with all versions of antlr4-runtime above 4.8

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

Irrelevant

How to reproduce the issue using our tutorial deployment?

Create some instance of MySqlAntlrDdlParser with antlr4-runtime with  version above 4.8

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

<Your answer>

Implementation ideas (optional)

<Your answer>