logging-log4j1
logging-log4j1 copied to clipboard
apache
Refine build scripts
This PR configures build and test scripts, so the project is buildable and testable with the current Maven and Java versions.
Note: this change does not alter the features, so I suggest merging this before other PRs that address CVEs.
Notable changes on top of Leo's commits in PR#17: a) I simplified toolchains: the build requires Java <= 1.8 or it requires Java 1.8 (exactly) toolchain to be present. b) I skipped "test: delete several broken low-quality tests". In practice, what Leo calls "broken tests" are tests that need to be executed in their own JVM (e.g. with special values for log4j.configuration, etc). I kept the tests in ignored mode.
/cc @lsimons
@jvz Sorry if this is stated somewhere I missed, but what's the reason for reversing the end-of-life decision for log4j 1.x?
@larrywest , log4j 1.2 is still used a lot, and there's no drop-in replacement. That is why fixing 1.2 makes perfect sense, so the users can just upgrade log4j 1.x to a newer version and avoid spending time on migrating to another libraries.
@larrywest There has not been a decision to reverse this. There has been a request to reverse it. We just realized that when we made the subversion repo read-only that there was mirror at GitHub that people were making PRs to. That GitHub repo was not under the control of the Apache Logging project so we moved it here. Discussions have been happening on the dev list and there is currently a vote in progress between two options. The Logging Services PMC hasn't committed to doing anything as of yet.
This PR should be closed.
See https://github.com/apache/logging-log4j1/blob/main/README.md for rationale.
See
- https://reload4j.qos.ch/
- https://github.com/qos-ch/reload4j for a maintained/released fork of similar improvements/fixes.
