Maven 3.10.0 removed org.fusesource.jansi:jansi from the classpath but still lists it as exportedArtifact #13726

Affected version

3.10.0

Bug description

Maven 3.10.0 removed org.fusesource.jansi:jansi from the classpath but
maven-core/src/main/resources/META-INF/maven/extension.xml
still contains
<exportedArtifact>org.fusesource.jansi:jansi</exportedArtifact>
and
<exportedPackage>org.fusesource.jansi.*</exportedPackage>

This breaks (at least) the jKube plugin (see jkube/issues/4019).

Even declaring jansi as a plugin dependency does not pull it into the classpath.
Adding the jansi jar to lib/ext solves the problem (which is no real option for CI pipelines).

I did not debugged this in detail, but the export declarations seem to filter jansi from the plugin's classpath.