-
Component Upgrade
-
Resolution: Done
-
Major
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
-
-
In 1.2.2.redhat-00002, we updated the shaded log4j:log4j from 1.2.17 to 1.2.17.redhat-00007 to keep the same target jdk version as jdk 8 by removing the specified target version. So all classes in the produced log4j-jboss-logmanager:1.2.2.Final-redhat-00002.jar are in the same target jdk version: 8.
Now in 1.3.1.Final-redhat-00002, the community version of log4j:log4j:1.2.17 is used, which has the target jdk version set to 1.4.
We need to rebuild log4j-jboss-logmanager:1.3.1.Final-00002 with the redhat version to keep it consistent.
- is incorporated by
-
JBEAP-28050 (7.4.z) Upgrade Wildfly Core from 15.0.39.Final-redhat-00001 to 15.0.40.Final-redhat-00002
- Resolved
- is related to
-
JBEAP-28267 (7.4.z) Upgrade jaxen from 1.1.6.redhat-2 to 1.1.6.redhat-00003
- Resolved
-
JBEAP-28277 (7.4.z) Upgrade byte-buddy from 1.11.12.redhat-00002 to 1.11.12.redhat-00003
- Resolved
- relates to
-
JBEAP-14935 (7.4.z) Class version of productized jaxen-1.1.6 is not synced to Java 8
- Resolved
-
JBEAP-14936 Class version of productized log4j-jboss-logmanager-1.1.4 is not synced to Java 6
- Closed
- links to
-
RHSA-2024:136880 Red Hat JBoss Enterprise Application Platform 7.4.20 Security update
-
RHSA-2024:136881 Red Hat JBoss Enterprise Application Platform 7.4.20 Security update
-
RHSA-2024:136882 Red Hat JBoss Enterprise Application Platform 7.4.20 Security update
-
RHSA-2024:136883 Red Hat JBoss Enterprise Application Platform 7.4.20 Security update