-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MS8] Branch main
overhaul #3
#2163
Comments
vy
added a commit
that referenced
this issue
Jan 10, 2024
vy
added a commit
that referenced
this issue
Jan 10, 2024
vy
added a commit
that referenced
this issue
Jan 10, 2024
vy
added a commit
that referenced
this issue
Jan 10, 2024
vy
added a commit
that referenced
this issue
Jan 10, 2024
vy
added a commit
that referenced
this issue
Jan 10, 2024
ppkarwasz
added a commit
to ppkarwasz/logging-log4j2
that referenced
this issue
Jan 12, 2024
This ports the changes to the `log4j-1.2-api` module that never made it to `main`. Part of apache#2163.
ppkarwasz
added a commit
to ppkarwasz/logging-log4j2
that referenced
this issue
Jan 15, 2024
This ports the changes to the `log4j-1.2-api` module that never made it to `main`. Part of apache#2163.
ppkarwasz
added a commit
to ppkarwasz/logging-log4j2
that referenced
this issue
Jan 15, 2024
This ports the changes to the `log4j-1.2-api` module that never made it to `main`. Part of apache#2163.
vy
added a commit
that referenced
this issue
Jan 15, 2024
vy
added a commit
that referenced
this issue
Jan 15, 2024
While working on #2227 I checked that no regressions are present in the |
This was referenced Jan 23, 2024
Merged
Checked and considered complete. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This story aims to overhaul
main
(targeting Log4j version3.0.0
) branch as a follow up of #1969 and #2016.Removal of deprecated features
main
, since it is forked from2.x
, contains several features and modules that are suitable to be dropped. Since this is a backward incompatible change, we cannot implement this for2.x
.main
, targeting3.0.0
, i.e., a new major version release, is a good opportunity for this. Following changes are mostly related with that.ThreadLocals.enable
property inmain
#2105DefaultLogEventFactory
(b338d07)Supplier
#2175log4j-layout-jackson
andlog4j-layout-jackson-xml
#2198StatusConsoleListener
filters #2226log4j-jcl
andlog4j-appserver
modules #2257Split functionality to dedicated modules
2.x
used to combine several features in one module:log4j-core
. This imposes, next to a greater surface for potential vulnerabilities, several disadvantages for those who only need a subset of these offered features. Here we try to improve this experience by moving certain functionalities to their own dedicated modules.log4j-core
#2106log4j-async
log4j-async-logger
#2241ConfigurationExtension
mechanism #2230log4j-async-logger
#2248Port changes from
2.x
main
was forked ~6 years ago from2.x
. In the meantime, thousands of improvements were introduced to2.x
and sadly a majority of these were not ported tomain
. Put another way,main
contains several issues that were already fixed in2.x
. Below shared items are related with porting such changes from2.x
tomain
.log4j-1.2-api
changes from2.x
#2188log4j-api
changes from2.x
#2208log4j-appserver
(75ab3ae)log4j-csv
✔️log4j-docker
(788ec71)log4j-flume-ng
(846f354, ca6f923)log4j-gctests
(245da43)log4j-iostreams
(4bd7e19)log4j-jcl
(40f1bde, a863232, b8fb8c8)log4j-jdbc
(14013cd)log4j-jdbc-dbcp2
(2b0ba72)log4j-jndi
(cf4b39e, 986a716)log4j-jndi-test
(c5680fe, bac23ba)log4j-layout-template-json
&log4j-layout-template-json-test
(027009e, 923a43e, 3254858, b1113c7)log4j-osgi
(e25c308, 496951e, 125f505, e3a2559)log4j-osgi-test
changes from2.x
#2187Miscellaneous improvements
In accordance with Boy Scout Rule, things we have improved along the way:
The text was updated successfully, but these errors were encountered: