Hi Ralph, On Sun, 18 Jun 2023 at 05:17, Ralph Goers <ralph.go...@dslextreme.com> wrote: > > This is a vote to release Log4j 3.0.0-alpha, the first release the Log4j 3.x > series. > > Please download, test, and cast your votes on the log4j developers list. > [] +1, release the artifacts > [] -1, don't release because... > > The vote will remain open for 72 hours. All votes are welcome and we > encourage everyone to test the release, but only Logging PMC votes are > “officially” counted. As always, at least 3 +1 votes and more positive than > negative votes are required.
I verified both the Git tag and source archive on a Debian box with: ./mvnw clean verify artifact:compare \ -Dreference.repo=https://repository.apache.org/content/repositories/orgapachelogging-1108/ \ -Dcompare.aggregate.only=true \ -DskipTests=true The artifacts are reproducible except: * The `Log4jPlugins.java` files are not reproducible due to https://github.com/apache/logging-log4j2/issues/1520 * `log4j-docker` and `log4j-kubernetes` have non reproducible OSGI headers (order of the exported packages). I have no idea what is the reason, * System specific `*.link` files (used by Exam 4 tests) end up in the `log4j-osgi` source archive. I deployed the `alpha1` artifacts to my test servers at work, with no problem so far. Considering it is an alpha release, it is a +1 from me. Piotr
