Environment (Required on creation):

• JBoss standalone webapp (used on JBoss EAP and Wildfly)

Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):

• The artifact contains SLF4J API 2.0.0-alpha1. It's an alpha release, we don't know about the stability. And it is an SLF4J version that is probably not fully compatible with what we expect in camunda-commons-logging.

Steps to reproduce (Required on creation):

• Build the JBoss standalone webapp with Java 11 (Does not occur with Java 8)

Observed Behavior (Required on creation):

• SLF4J API 2.0.0-alpha1 is included in the WAR

Expected behavior (Required on creation):

• SLF4J API 1.7 is included in the WAR

Root Cause (Required on prioritization):

• With CAM-13519 we have added a dependency to Hikari 4.0.3. This has two Maven profiles activated by Java versions that switch the SLF4J API version. Since we also switched our assembly build to Java 11, this problem occurs on the current master branch.

Solution Ideas (Optional):

• Exclude the SLF4J dependency from Hikari (since it already comes with commons-logging and other dependencies in version 1.7)

Hints (optional):

• This was reported in the Hikari project but not addressed by project maintainers so far: https://github.com/brettwooldridge/HikariCP/issues/1746