The installation of Eclipse Groovy 4.2.0 and higher forces the removal of the m2e slf4j-over-logback plugin causing Maven logs to be no longer available in the console view.

It appears that there is a story behind that related to a change in the classloaders in Eclipse 4.19 and that at least one group has been able to address the issue by internalizing its logback dependency.

Maybe m2e can also be adjusted such that the separate m2e slf4j-over-logback bundle is no longer required and thus also removing the problems with Groovy / Eclipse classloading?

Related issues:

• Groovy Eclipse 4.2.0 <-> m2e console groovy/groovy-eclipse#1275
• Incompatibility between Groovy Eclipse Plugin and PMD Plugin pmd/pmd-eclipse-plugin#134
• Eclipse 2021-03 (4.19) won't start after installing https://dist.springsource.org/snapshot/GRECLIPSE/e4.19 groovy/groovy-eclipse#1237
• https://bugs.eclipse.org/bugs/show_bug.cgi?id=574922 (logback-classic bundle definition causes problems for multiple downstream projects)
• https://jira.qos.ch/browse/LOGBACK-1564 (Issue complex around logback and various Eclipse/OSGI projects)