Customer have some problems with batch client logging with message : 

SLF4J: No SLF4J providers were found.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See

https://www.slf4j.org/codes.html#noProviders

for further details.

In investigation revealed that wildfly-elytron package includes slf4j-api classes. This was not problem with wildfly-elytron-2.2.7.Final-redhat-00001.jar

where META-INF/maven/org.slf4j/slf4j-api/pom.xml
has

<parent>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-parent</artifactId>
<version>2.0.7.redhat-00003</version>
</parent>

but when library was updated to wildfly-elytron-2.2.9.Final-redhat-00001.jar same file META-INF/maven/org.slf4j/slf4j-api/pom.xml reveals

<parent>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-parent</artifactId>
<version>1.7.32</version>
</parent>

This seems like packaging error. Can you confirm this and advise if there is wildfly-elytron package version 2.2.9 with slf4j-api 2.0.x?

That does look likely to be a bug.All of our artifacts should be built from redhat versions, not 3rd party upstream versions.

So getting that pom.xml into the final build with an upstream version looks like it may be probably built wrong.