Platform:

• Android -> If yes, which Device API (and compileSdkVersion/targetSdkVersion/Build tools) version?
• [x ] Java -> If yes, which Java 11
• Kotlin -> If yes, which Kotlin (and jvmTarget) version?
• NDK -> If yes, which NDK/CMake version?
• React-Native -> If yes, which version?
• Timber -> If yes, which version?
• [x ] Log4j2 -> If yes, which version? 3.13
• Logback -> If yes, which version?
• Spring -> If yes, which version?

IDE:

• Android Studio -> If yes, which version?
• [x ] IntelliJ -> If yes, which version? 2020.2
• Other -> If yes, which one?

Build system:

• Gradle -> If yes, which version?
• Buck -> If yes, which version?
• Bazel -> If yes, which version?
• [x ] Maven -> If yes, which version?
• Other -> If yes, which one?

Android Gradle Plugin:

• Yes -> If yes, which version?
• [ x] No

Sentry Android Gradle Plugin:

• Yes -> If yes, which version?
• [x ] No

Proguard/R8:

• Enabled
• [x ] Disabled

Platform installed with:

• JCenter
• Bintray
• [x ] Maven Central
• Manually

The version of the SDK:
3.x.x

I have the following issue:
The legacyAPI contained a java.util.logging Logger Handler named io.sentry.jul.SentryHander. This class has been dropped for API 3.x.x Is there a specific reasoning for this?
The lack of such a handler makes the integration of Sentry into wildfly much more difficult (if you want Sentry to be active during startup/deployment) because the wildfly container only allows custom handlers that extend java.util.logging.Handler (ref)

Steps to reproduce:
Checkout the new java-sentry api

Actual result:
There is no jul handler.

Expected result:
A handler extending java.util.logger.Handler should exist