Update log4j-jul to Java 17

We update `log4j-jul` to:

- implement methods introduced in Java 9,
- remove methods deprecated in Java 9.

Author: ppkarwasz

log4j-jul/pom.xml

@@ -28,57 +28,48 @@
   <name>Apache Log4j JUL Adapter</name>
   <description>The Apache Log4j implementation of java.util.logging</description>
 
-  <properties>
-    <log4jParentDir>${basedir}/..</log4jParentDir>
-
-    <!--
-      ~ OSGi and JPMS options
-      -->
-    <bnd-extra-package-options>
-      <!-- Log4j Core is optional -->
-      org.apache.logging.log4j.core.*;resolution:=optional
-    </bnd-extra-package-options>
-
-    <!-- PTS requires using the JUnit Platform, which interferes with JUL initialization -->
-    <predictive.test.selection.enabled>false</predictive.test.selection.enabled>
-  </properties>
-
   <dependencies>
+
     <dependency>
       <groupId>org.apache.logging.log4j</groupId>
       <artifactId>log4j-api</artifactId>
     </dependency>
+
     <dependency>
       <groupId>org.apache.logging.log4j</groupId>
-      <artifactId>log4j-core</artifactId>
-      <optional>true</optional>
+      <artifactId>log4j-kit</artifactId>
     </dependency>
+
     <dependency>
       <groupId>org.assertj</groupId>
       <artifactId>assertj-core</artifactId>
       <scope>test</scope>
     </dependency>
-    <!-- Required for AsyncLogger testing -->
-    <dependency>
-      <groupId>com.lmax</groupId>
-      <artifactId>disruptor</artifactId>
-      <scope>test</scope>
-    </dependency>
+
     <dependency>
       <groupId>org.hamcrest</groupId>
       <artifactId>hamcrest</artifactId>
       <scope>test</scope>
     </dependency>
+
     <dependency>
       <groupId>junit</groupId>
       <artifactId>junit</artifactId>
       <scope>test</scope>
     </dependency>
+
     <dependency>
       <groupId>org.apache.logging.log4j</groupId>
       <artifactId>log4j-async-logger</artifactId>
       <scope>test</scope>
     </dependency>
+
+    <dependency>
+      <groupId>org.apache.logging.log4j</groupId>
+      <artifactId>log4j-core</artifactId>
+      <scope>test</scope>
+    </dependency>
+
     <dependency>
       <groupId>org.apache.logging.log4j</groupId>
       <artifactId>log4j-core-test</artifactId>

log4j-jul/src/main/java/org/apache/logging/log4j/jul/AbstractLoggerAdapter.java

@@ -22,9 +22,22 @@
 import org.apache.logging.log4j.util.StackLocatorUtil;
 
 /**
- * Abstract Logger registry. Due to the optionality of using log4j-core, there are two registries available at runtime
- * to create: {@link ApiLoggerAdapter} and {@link CoreLoggerAdapter}.
+ * Abstract Logger registry.
+ * <p>
+ *     JUL contains methods, such as {@link Logger#setLevel}, which modify the configuration of the logging backend.
+ *     To fully implement all {@code Logger} methods, we need to provide a different {@code Logger} implementation
+ *     for each Log4j API implementation.
+ * </p>
+ * <p>
+ *     Older Log4j versions provided an alternative {@code CoreLoggerAdapter} implementation that supported
+ *     the modification of Log4j Core configuration using JUL.
+ * </p>
+ *     Since version 2.24.0, however, this implementation was deprecated for removal.
+ *     If you wish to enable this feature again, you need to implement this class and provide its FQCN
+ *     as {@code log4j.jul.loggerAdapter} configuration property.
+ * </p>
  *
+ * @see <a href="https://github.com/apache/logging-log4j2/issues/2353">Issue #2353</a>
  * @since 2.1
  */
 public abstract class AbstractLoggerAdapter extends org.apache.logging.log4j.spi.AbstractLoggerAdapter<Logger> {