Probably not a blocker but the sha512 file can't be validated with the usual:
$ shasum --check apache-log4j-jmx-gui-2.21.0-src.zip.sha512 Instead I get: shasum: /tmp/apache-log4j-jmx-gui-2.21.0-src.zip: No such file or directory /tmp/apache-log4j-jmx-gui-2.21.0-src.zip: FAILED open or read shasum: WARNING: 1 listed file could not be read Because the sha512 file points to a non-existent folder "tmp" instead pointing directly to the file: $ cat apache-log4j-jmx-gui-2.21.0-src.zip.sha512 5f1847021946f22a6a7e5b40ac9a409039bcb2fae668cf70439c814df4a5a6f770fef6b628c91e1dc317c7f684d5b1d13fdc112bd6369b16eff64e4ae1084474 /tmp/apache-log4j-jmx-gui-2.21.0-src.zip and eye-balling a sha512 is not "fun" ;-) Gary On 2023/09/15 08:54:45 Volkan Yazıcı wrote: > This is a vote to release the Apache Log4j JMX GUI 2.21.0 (RC2). > > Source repository: https://github.com/apache/logging-log4j-jmx-gui > Commit: c3056b340f57e2d6bd66b9f825722c336090d0d2 > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-jmx-gui > Nexus: > https://repository.apache.org/content/repositories/orgapachelogging-1175 > Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 > > Please download, test, and cast your votes on this mailing list. > > [ ] +1, release the artifacts > [ ] -1, don't release, because... > > This vote is open for 24 hours and will pass unless getting a > net negative vote count. All votes are welcome and we encourage > everyone to test the release, but only the Logging Services PMC > votes are officially counted. At least 3 +1 votes and more > positive than negative votes are required. > > # RC1..RC2 changes > > - Added `Main-Class` to `MANIFEST.MF` > > # Release Notes > > This marks the first release where the Log4j JMX GUI is released > separately from the Log4j itself. > > ## Changes > > ### Added > > * Project is moved to a new repository[1] with its own release cycle > > [1] https://github.com/apache/logging-log4j-jmx-gui >
