gpg --import KEYS
gpg --verify apache-log4j-3.0.0-beta2-bin.zip.ascDownload Apache Log4j 2
Apache Log4j 3 is distributed under the Apache License, version 2.0.
The link in the Mirrors column should display a list of available mirrors with a default selection based on your inferred location. If you do not see that page, try a different browser. The checksum and signature are links to the originals on the main distribution server.
| Distribution | Mirrors | Checksum | Signature |
|---|---|---|---|
Apache Log4j 3.x binary (tar.gz) |
|||
Apache Log4j 3.x binary (zip) |
|||
Apache Log4j 3.x source (tar.gz) |
|||
Apache Log4j 3.x source (zip) |
It is essential that you verify the integrity of the downloaded files using the PGP or SHA512 signatures. Please read Verifying Apache HTTP Server Releases for more information on why you should verify our releases.
The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the asc signature file for the relevant distribution. Make sure you get these files from the main distribution directory, rather than from a mirror. Then verify the signatures using
Alternatively, you can verify the SHA512 signature on the files. A unix program called sha512sum is included in many unix distributions.
Requirements
Log4j 3 runtime requires a minimum of Java 17. See the Log4j 2 website for the latest releases supporting Java 6, 7, and 8.
Previous Releases
All previous releases of Apache log4j can be found in the ASF archive repository. Of course, all releases are availble for use as dependencies from the Maven Central Repository
Using Log4j on your classpath
To use Log4j 3.x in your application make sure that the API, Plugins, and Core jars are in the application’s classpath. Add the dependencies listed below to your classpath.
-
log4j-api-3.0.0-beta2.jar
-
log4j-plugins-3.0.0-beta2.jar
-
log4j-core-3.0.0-beta2.jar
You can do this from the command line or a manifest file.