Re: [VOTE] Release Apache Log4j 2.22.0

[Gary D. Gregory]

Hi,

The only way I could get the build to pass is to let 'mvn clean verify' run 
while I went to lunch and nothing else was running.

I would not in want to vote without running all the tests.

+1

Gary

On 2023/11/17 14:16:14 Volkan Yazıcı wrote:
> File-based tests on Windows are not stable.
> Occasionally they have hiccups.
> Would you mind retrying, please?
> 
> You can speed up the process as follows:
> 
> # Install everything without any checks
> ./mvnw install -DskipTests -Dspotbugs.skip -Dspotless.skip
> 
> # Verify everything except `log4j-core-test`
> ./mvnw verify -pl \!:log4j-core-test
> 
> # Verify only `log4j-core-test`
> ./mvnw verify -pl :log4j-core-test
> 
> On Fri, Nov 17, 2023 at 3:03 PM Gary D. Gregory  wrote:
> >
> > Build failure for me on Windows from the src zip and 'mvn clean verify':
> >
> > [ERROR] Failures:
> > [ERROR]   RollingAppenderDeleteMaxDepthTest.testAppender:73 
> > [target\rolling-with-delete-depth\test\1, 
> > target\rolling-with-delete-depth\test\2, 
> > target\rolling-with-delete-depth\test\test-1.log, 
> > target\rolling-with-delete-depth\test\test-2.log, 
> > target\rolling-with-delete-depth\test\test-3.log, 
> > target\rolling-with-delete-depth\test\test-4.log] expected:<5> but was:<6>
> > [ERROR]   RollingAppenderDeleteScriptTest.testAppender:73 
> > target\rolling-with-delete-script\test\test-2.log should have odd index
> > [ERROR]   
> > AsyncThreadContextCopyOnWriteTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:171->AbstractAsyncThreadContextTestBase.checkResult:204
> >  [Log file 'AsyncLoggerTest.log']
> > expected: "INFO c.f.Bar mapvalue [stackvalue] {KEY=mapvalue, 
> > configProp=configValue, configProp2=configValue2} COPY_ON_WRITE 
> > CopyOnWriteSortedArrayThreadContextMap AsyncLoggerContext i=0"
> >  but was: "INFO c.f.Bar mapvalue [stackvalue, stackvalue] {KEY=mapvalue, 
> > configProp=configValue, configProp2=configValue2} COPY_ON_WRITE 
> > CopyOnWriteSortedArrayThreadContextMap AsyncLoggerContext i=0"
> > [ERROR]   
> > AsyncThreadContextGarbageFreeTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:171->AbstractAsyncThreadContextTestBase.checkResult:204
> >  [Log file 'AsyncLoggerTest.log']
> > expected: "INFO c.f.Bar mapvalue [stackvalue] {KEY=mapvalue, 
> > configProp=configValue, configProp2=configValue2} GARBAGE_FREE 
> > GarbageFreeSortedArrayThreadContextMap AsyncLoggerContext i=0"
> >  but was: "INFO c.f.Bar mapvalue [stackvalue, stackvalue] {KEY=mapvalue, 
> > configProp=configValue, configProp2=configValue2} GARBAGE_FREE 
> > GarbageFreeSortedArrayThreadContextMap AsyncLoggerContext i=0"
> > [ERROR] Errors:
> > [ERROR]   
> > AsyncThreadContextCopyOnWriteTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:159
> >  » ConditionTimeout Condition with lambda expression in 
> > org.apache.logging.log4j.core.async.AbstractAsyncThreadContextTestBase that 
> > uses org.apache.logging.log4j.core.jmx.RingBufferAdmin was not fulfilled 
> > within 500 milliseconds.
> > [ERROR]   
> > AsyncThreadContextGarbageFreeTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:159
> >  » ConditionTimeout Condition with lambda expression in 
> > org.apache.logging.log4j.core.async.AbstractAsyncThreadContextTestBase that 
> > uses org.apache.logging.log4j.core.jmx.RingBufferAdmin was not fulfilled 
> > within 500 milliseconds.
> > [INFO]
> > [ERROR] Tests run: 2452, Failures: 4, Errors: 2, Skipped: 35
> >
> > All that I could capture in the console is here: 
> > https://paste.apache.org/k6auj
> >
> > - Testing src zip file
> > - OK: ASC verify
> > - OK SHA check
> > - mvn clean verify
> >
> > Using:
> >
> > Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
> > Maven home: C:\java\apache-maven-3.9.5
> > Java version: 11.0.20, vendor: Eclipse Adoptium, runtime: C:\Program 
> > Files\Eclipse Adoptium\jdk-11.0.20.8-hotspot
> > Default locale: en_US, platform encoding: Cp1252
> > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> > Microsoft Windows [Version 10.0.19045.3570]
> >
> > Gary
> >
> > On 2023/11/17 12:07:06 Volkan Yazıcı wrote:
> > > This is a vote to release the Apache Log4j 2.22.0.
> > >
> > > Website: https://logging.staged.apache.org/log4j
> > > GitHub: https://github.com/apache/logging-log4j2
> > > Commit: a1634d695e5702ecab505fea5aadaf9890641487
> > > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j
> > > Nexus: 
> > > https://repository.apache.org/content/repositories/orgapachelogging-1238
> > > 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 72 hours and will pass unless getting a
> > > net negative vote count. All votes are welcome and we e

Re: [PR] Bump org.junit:junit-bom from 5.10.0 to 5.10.1 [logging-log4j-jakarta]

[via GitHub]

github-actions[bot] commented on PR #1:
URL: 
https://github.com/apache/logging-log4j-jakarta/pull/1#issuecomment-1817035848

   Changes are applied by CI in 6fb89eb4d389963b6e5f95fca1ae0cff5bbab592


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump org.junit:junit-bom from 5.10.0 to 5.10.1 [logging-log4j-jakarta]

[via GitHub]

github-actions[bot] closed pull request #1: Bump org.junit:junit-bom from 
5.10.0 to 5.10.1
URL: https://github.com/apache/logging-log4j-jakarta/pull/1


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump org.junit:junit-bom from 5.10.0 to 5.10.1 [logging-log4j-jakarta]

[via GitHub]

ppkarwasz commented on PR #1:
URL: 
https://github.com/apache/logging-log4j-jakarta/pull/1#issuecomment-1817028310

   @dependabot recreate


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump org.mockito:mockito-bom from 5.5.0 to 5.7.0 [logging-log4j-jakarta]

[via GitHub]

github-actions[bot] closed pull request #3: Bump org.mockito:mockito-bom from 
5.5.0 to 5.7.0
URL: https://github.com/apache/logging-log4j-jakarta/pull/3


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump org.mockito:mockito-bom from 5.5.0 to 5.7.0 [logging-log4j-jakarta]

[via GitHub]

github-actions[bot] commented on PR #3:
URL: 
https://github.com/apache/logging-log4j-jakarta/pull/3#issuecomment-1816996007

   Changes are applied by CI in f6bbf6258ee43d60118cd0a4e1a9fda99a560e28


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump org.springframework:spring-framework-bom from 6.0.13 to 6.1.0 [logging-log4j-jakarta]

[via GitHub]

github-actions[bot] closed pull request #4: Bump 
org.springframework:spring-framework-bom from 6.0.13 to 6.1.0
URL: https://github.com/apache/logging-log4j-jakarta/pull/4


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [PR] Bump org.springframework:spring-framework-bom from 6.0.13 to 6.1.0 [logging-log4j-jakarta]

[via GitHub]

github-actions[bot] commented on PR #4:
URL: 
https://github.com/apache/logging-log4j-jakarta/pull/4#issuecomment-1816983082

   Changes are applied by CI in 4ca37fae4e0594bd9dc5ed4e5c069f69faf23df2


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[log4j] Moving Jakarta in `main` to a separate repository

[Volkan Yazıcı]

I am working on #1966 ,
which aims to move the Jakarta-related components of Log4j 3 to a separate
repository. I have

   1. moved `log4j-jakarta-{web,smtp}` and `log4j-jms` to the
   `logging-log4j-jakarta` repository
   
   2. migrated `log4j-jms` to a new Jakarta-based `log4j-jakarta-jms` module
   3. overhauled the documentation
   4. created the project website
   

Piotr helped me with `log4j-jakarta-web` docs and sync'ing code from `2.x`
branch.

In `main` many of the properties don't might not work the way they are
documented. I told Ralph about this and he stated he will take a look.

I will proceed with removing the following components from `main` and
provide sufficient pointers wherever needed:

   1. `log4j-jakarta-smtp`
   2. `log4j-jakarta-web`
   3. `log4j-jms`
   4. `log4j-smtp`
   5. `log4j-web`

This work is part of #1951
, which removes
modules from `main` that were deprecated in `2.x`.

Re: [VOTE] Release Apache Log4j 2.22.0

[Volkan Yazıcı]

File-based tests on Windows are not stable.
Occasionally they have hiccups.
Would you mind retrying, please?

You can speed up the process as follows:

# Install everything without any checks
./mvnw install -DskipTests -Dspotbugs.skip -Dspotless.skip

# Verify everything except `log4j-core-test`
./mvnw verify -pl \!:log4j-core-test

# Verify only `log4j-core-test`
./mvnw verify -pl :log4j-core-test

On Fri, Nov 17, 2023 at 3:03 PM Gary D. Gregory  wrote:
>
> Build failure for me on Windows from the src zip and 'mvn clean verify':
>
> [ERROR] Failures:
> [ERROR]   RollingAppenderDeleteMaxDepthTest.testAppender:73 
> [target\rolling-with-delete-depth\test\1, 
> target\rolling-with-delete-depth\test\2, 
> target\rolling-with-delete-depth\test\test-1.log, 
> target\rolling-with-delete-depth\test\test-2.log, 
> target\rolling-with-delete-depth\test\test-3.log, 
> target\rolling-with-delete-depth\test\test-4.log] expected:<5> but was:<6>
> [ERROR]   RollingAppenderDeleteScriptTest.testAppender:73 
> target\rolling-with-delete-script\test\test-2.log should have odd index
> [ERROR]   
> AsyncThreadContextCopyOnWriteTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:171->AbstractAsyncThreadContextTestBase.checkResult:204
>  [Log file 'AsyncLoggerTest.log']
> expected: "INFO c.f.Bar mapvalue [stackvalue] {KEY=mapvalue, 
> configProp=configValue, configProp2=configValue2} COPY_ON_WRITE 
> CopyOnWriteSortedArrayThreadContextMap AsyncLoggerContext i=0"
>  but was: "INFO c.f.Bar mapvalue [stackvalue, stackvalue] {KEY=mapvalue, 
> configProp=configValue, configProp2=configValue2} COPY_ON_WRITE 
> CopyOnWriteSortedArrayThreadContextMap AsyncLoggerContext i=0"
> [ERROR]   
> AsyncThreadContextGarbageFreeTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:171->AbstractAsyncThreadContextTestBase.checkResult:204
>  [Log file 'AsyncLoggerTest.log']
> expected: "INFO c.f.Bar mapvalue [stackvalue] {KEY=mapvalue, 
> configProp=configValue, configProp2=configValue2} GARBAGE_FREE 
> GarbageFreeSortedArrayThreadContextMap AsyncLoggerContext i=0"
>  but was: "INFO c.f.Bar mapvalue [stackvalue, stackvalue] {KEY=mapvalue, 
> configProp=configValue, configProp2=configValue2} GARBAGE_FREE 
> GarbageFreeSortedArrayThreadContextMap AsyncLoggerContext i=0"
> [ERROR] Errors:
> [ERROR]   
> AsyncThreadContextCopyOnWriteTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:159
>  » ConditionTimeout Condition with lambda expression in 
> org.apache.logging.log4j.core.async.AbstractAsyncThreadContextTestBase that 
> uses org.apache.logging.log4j.core.jmx.RingBufferAdmin was not fulfilled 
> within 500 milliseconds.
> [ERROR]   
> AsyncThreadContextGarbageFreeTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:159
>  » ConditionTimeout Condition with lambda expression in 
> org.apache.logging.log4j.core.async.AbstractAsyncThreadContextTestBase that 
> uses org.apache.logging.log4j.core.jmx.RingBufferAdmin was not fulfilled 
> within 500 milliseconds.
> [INFO]
> [ERROR] Tests run: 2452, Failures: 4, Errors: 2, Skipped: 35
>
> All that I could capture in the console is here: 
> https://paste.apache.org/k6auj
>
> - Testing src zip file
> - OK: ASC verify
> - OK SHA check
> - mvn clean verify
>
> Using:
>
> Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
> Maven home: C:\java\apache-maven-3.9.5
> Java version: 11.0.20, vendor: Eclipse Adoptium, runtime: C:\Program 
> Files\Eclipse Adoptium\jdk-11.0.20.8-hotspot
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Microsoft Windows [Version 10.0.19045.3570]
>
> Gary
>
> On 2023/11/17 12:07:06 Volkan Yazıcı wrote:
> > This is a vote to release the Apache Log4j 2.22.0.
> >
> > Website: https://logging.staged.apache.org/log4j
> > GitHub: https://github.com/apache/logging-log4j2
> > Commit: a1634d695e5702ecab505fea5aadaf9890641487
> > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j
> > Nexus: 
> > https://repository.apache.org/content/repositories/orgapachelogging-1238
> > 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 72 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.
> >
> > == Review kit
> >
> > The minimum set of steps needed to review the uploaded distribution
> > files can be summarized as follows:
> >
> > # Verify checksums
> > shasum --check *.sha512
> >
> > # Verify signatures
> > for sigFile in *.asc; do gpg --verify $sigFile; done
> >
> > # Verify reproduciblity
> > umask 0022
> > unzip *-src

Re: [VOTE] Release Apache Log4j 2.22.0

[Gary D. Gregory]

Build failure for me on Windows from the src zip and 'mvn clean verify':

[ERROR] Failures:
[ERROR]   RollingAppenderDeleteMaxDepthTest.testAppender:73 
[target\rolling-with-delete-depth\test\1, 
target\rolling-with-delete-depth\test\2, 
target\rolling-with-delete-depth\test\test-1.log, 
target\rolling-with-delete-depth\test\test-2.log, 
target\rolling-with-delete-depth\test\test-3.log, 
target\rolling-with-delete-depth\test\test-4.log] expected:<5> but was:<6>
[ERROR]   RollingAppenderDeleteScriptTest.testAppender:73 
target\rolling-with-delete-script\test\test-2.log should have odd index
[ERROR]   
AsyncThreadContextCopyOnWriteTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:171->AbstractAsyncThreadContextTestBase.checkResult:204
 [Log file 'AsyncLoggerTest.log']
expected: "INFO c.f.Bar mapvalue [stackvalue] {KEY=mapvalue, 
configProp=configValue, configProp2=configValue2} COPY_ON_WRITE 
CopyOnWriteSortedArrayThreadContextMap AsyncLoggerContext i=0"
 but was: "INFO c.f.Bar mapvalue [stackvalue, stackvalue] {KEY=mapvalue, 
configProp=configValue, configProp2=configValue2} COPY_ON_WRITE 
CopyOnWriteSortedArrayThreadContextMap AsyncLoggerContext i=0"
[ERROR]   
AsyncThreadContextGarbageFreeTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:171->AbstractAsyncThreadContextTestBase.checkResult:204
 [Log file 'AsyncLoggerTest.log']
expected: "INFO c.f.Bar mapvalue [stackvalue] {KEY=mapvalue, 
configProp=configValue, configProp2=configValue2} GARBAGE_FREE 
GarbageFreeSortedArrayThreadContextMap AsyncLoggerContext i=0"
 but was: "INFO c.f.Bar mapvalue [stackvalue, stackvalue] {KEY=mapvalue, 
configProp=configValue, configProp2=configValue2} GARBAGE_FREE 
GarbageFreeSortedArrayThreadContextMap AsyncLoggerContext i=0"
[ERROR] Errors:
[ERROR]   
AsyncThreadContextCopyOnWriteTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:159
 » ConditionTimeout Condition with lambda expression in 
org.apache.logging.log4j.core.async.AbstractAsyncThreadContextTestBase that 
uses org.apache.logging.log4j.core.jmx.RingBufferAdmin was not fulfilled within 
500 milliseconds.
[ERROR]   
AsyncThreadContextGarbageFreeTest.testAsyncLogWritesToLog:35->AbstractAsyncThreadContextTestBase.testAsyncLogWritesToLog:159
 » ConditionTimeout Condition with lambda expression in 
org.apache.logging.log4j.core.async.AbstractAsyncThreadContextTestBase that 
uses org.apache.logging.log4j.core.jmx.RingBufferAdmin was not fulfilled within 
500 milliseconds.
[INFO]
[ERROR] Tests run: 2452, Failures: 4, Errors: 2, Skipped: 35

All that I could capture in the console is here: https://paste.apache.org/k6auj

- Testing src zip file
- OK: ASC verify
- OK SHA check
- mvn clean verify

Using:

Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
Maven home: C:\java\apache-maven-3.9.5
Java version: 11.0.20, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-11.0.20.8-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Microsoft Windows [Version 10.0.19045.3570]

Gary

On 2023/11/17 12:07:06 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j 2.22.0.
> 
> Website: https://logging.staged.apache.org/log4j
> GitHub: https://github.com/apache/logging-log4j2
> Commit: a1634d695e5702ecab505fea5aadaf9890641487
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1238
> 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 72 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.
> 
> == Review kit
> 
> The minimum set of steps needed to review the uploaded distribution
> files can be summarized as follows:
> 
> # Verify checksums
> shasum --check *.sha512
> 
> # Verify signatures
> for sigFile in *.asc; do gpg --verify $sigFile; done
> 
> # Verify reproduciblity
> umask 0022
> unzip *-src.zip -d src
> cd src
> export 
> NEXUS_REPO=https://repository.apache.org/content/repositories/orgapachelogging-1238
> sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO
> 
> == Release notes
> 
> This release provides a CycloneDX Software Bill of Materials (SBOM)[1]
> along with each artifact and contains bug fixes addressing issues in
> the JPMS & OSGi infrastructure overhauled in `2.21.0`, dependency
> updates, and some other minor fixes and improvements.
> 
> [1] https://cyclonedx.org/capabilities/sbom
> 
> === CycloneDX Software Bill of Materials (SBOM)
> 
> This is the first Log4j release that provides a CycloneDX 

Re: [VOTE] Release Apache Log4j Tools 0.6.0

[Volkan Yazıcı]

`log4j-tools-bom:0.5.0` is broken: `parent` is missing.
This release (i.e., `0.6.0`) fixes that.

On Fri, Nov 17, 2023 at 2:11 PM Gary D. Gregory  wrote:
>
> Seen during 'mvn clean verify'
>
> [INFO] --- log4j-changelog:0.5.0:export (export-changelog) @ log4j-tools-bom 
> ---
> [WARNING] The POM for org.apache.logging.log4j:log4j-changelog:jar:0.5.0 is 
> invalid, transitive dependencies (if any) will not be available, enable debug 
> logging for more details
> exported 6 release directories: ..., `C:\tmp\test\src\changelog\0.6.0`
> exporting upcoming release directory: `C:\tmp\test\src\changelog\.0.x.x`
>
> Is that important? What doe sit mean?
>
> TY!
> Gary
>
>
> On 2023/11/15 15:03:13 Volkan Yazıcı wrote:
> > This is a vote to release the Apache Log4j Tools 0.6.0.
> >
> > Website: https://logging.staged.apache.org/log4j/tools
> > GitHub: https://github.com/apache/logging-log4j-tools
> > Commit: 18425d95a4d150de905929d55bf55545d70f3d91
> > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
> > Nexus: 
> > https://repository.apache.org/content/repositories/orgapachelogging-1233
> > 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 72 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.
> >
> > === Release Notes
> >
> > This minor release contains various bug fixes and improvements.
> >
> >  Added
> >
> > * Started generating CycloneDX SBOM with the recent update of
> > `logging-parent` to version `10.4.0`
> >
> >  Changed
> >
> > * Update `org.apache.logging:logging-parent` to version `10.4.0`
> >
> >  Fixed
> >
> > * `log4j-tools-bom` was broken due to removed `parent` during
> > flattening. This is automatically fixed by the recent `logging-parent`
> > version `10.4.0` update.
> >

Re: [VOTE] Release Apache Log4j Tools 0.6.0

[Volkan Yazıcı]

Good catch.
Though not a big issue; `spotbugs-annotations` dependency is missing.
Fixed in `main` via `fb6fee27b349bb7ec5e847a6d33f9abb81b714ec`.

On Fri, Nov 17, 2023 at 2:12 PM Gary D. Gregory  wrote:
>
> Also seen during 'mvn clean verify':
>
> [INFO] --- compiler:3.11.0:compile (default-compile) @ 
> log4j-changelog-maven-plugin ---
> [INFO] Changes detected - recompiling the module! :dependency
> [INFO] Compiling 5 source files with javac [debug release 8] to target\classes
> [WARNING] Cannot find annotation method 'value()' in type 
> 'edu.umd.cs.findbugs.annotations.SuppressFBWarnings': class file for 
> edu.umd.cs.findbugs.annotations.SuppressFBWarnings not found
>
>
> Gary
>
> On 2023/11/15 15:03:13 Volkan Yazıcı wrote:
> > This is a vote to release the Apache Log4j Tools 0.6.0.
> >
> > Website: https://logging.staged.apache.org/log4j/tools
> > GitHub: https://github.com/apache/logging-log4j-tools
> > Commit: 18425d95a4d150de905929d55bf55545d70f3d91
> > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
> > Nexus: 
> > https://repository.apache.org/content/repositories/orgapachelogging-1233
> > 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 72 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.
> >
> > === Release Notes
> >
> > This minor release contains various bug fixes and improvements.
> >
> >  Added
> >
> > * Started generating CycloneDX SBOM with the recent update of
> > `logging-parent` to version `10.4.0`
> >
> >  Changed
> >
> > * Update `org.apache.logging:logging-parent` to version `10.4.0`
> >
> >  Fixed
> >
> > * `log4j-tools-bom` was broken due to removed `parent` during
> > flattening. This is automatically fixed by the recent `logging-parent`
> > version `10.4.0` update.
> >

Re: [VOTE] Release Apache Log4j Tools 0.6.0 (RC2)

[Gary D. Gregory]

+1

Same warnings as noted previously.

- Testing src zip file
- OK: ASC verify
- OK: SHA check
- OK: mvn clean verify

Using:

Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
Maven home: C:\java\apache-maven-3.9.5
Java version: 17.0.8, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-17.0.8.7-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Microsoft Windows [Version 10.0.19045.3570]

Gary

On 2023/11/17 09:21:48 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j Tools 0.6.0 (RC2).
> 
> Website: https://logging.staged.apache.org/log4j/tools
> GitHub: https://github.com/apache/logging-log4j-tools
> Commit: a696e081304cc0693d86533013df5b4d886cfb9c
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1237
> 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.
> 
> === Note on 24 hours deadline
> 
> RC1 vote was created 2 days ago. RC2 only contains missing CycloneDX
> SBOMs in the distribution archived by ASF. Note that SBOMs in the
> Nexus were already working in RC1. Hence, an extra 24 hours would make
> it all add up to 72 hours.
> 
> === Release Notes
> 
> This minor release contains various bug fixes and improvements.
> 
>  Added
> 
> * Started generating CycloneDX SBOM with the recent update of
> `logging-parent` to version `10.4.0`
> 
>  Changed
> 
> * Update `org.apache.logging:logging-parent` to version `10.4.0`
> 
>  Fixed
> 
> * `log4j-tools-bom` was broken due to removed `parent` during
> flattening. This is automatically fixed by the recent `logging-parent`
> version `10.4.0` update.
> 

Re: [VOTE] Release Apache Log4j Tools 0.6.0

[Gary D. Gregory]

Also seen during 'mvn clean verify':

[INFO] --- compiler:3.11.0:compile (default-compile) @ 
log4j-changelog-maven-plugin ---
[INFO] Changes detected - recompiling the module! :dependency
[INFO] Compiling 5 source files with javac [debug release 8] to target\classes
[WARNING] Cannot find annotation method 'value()' in type 
'edu.umd.cs.findbugs.annotations.SuppressFBWarnings': class file for 
edu.umd.cs.findbugs.annotations.SuppressFBWarnings not found


Gary

On 2023/11/15 15:03:13 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j Tools 0.6.0.
> 
> Website: https://logging.staged.apache.org/log4j/tools
> GitHub: https://github.com/apache/logging-log4j-tools
> Commit: 18425d95a4d150de905929d55bf55545d70f3d91
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1233
> 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 72 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.
> 
> === Release Notes
> 
> This minor release contains various bug fixes and improvements.
> 
>  Added
> 
> * Started generating CycloneDX SBOM with the recent update of
> `logging-parent` to version `10.4.0`
> 
>  Changed
> 
> * Update `org.apache.logging:logging-parent` to version `10.4.0`
> 
>  Fixed
> 
> * `log4j-tools-bom` was broken due to removed `parent` during
> flattening. This is automatically fixed by the recent `logging-parent`
> version `10.4.0` update.
> 

Re: [VOTE] Release Apache Log4j Tools 0.6.0

[Gary D. Gregory]

Seen during 'mvn clean verify'

[INFO] --- log4j-changelog:0.5.0:export (export-changelog) @ log4j-tools-bom ---
[WARNING] The POM for org.apache.logging.log4j:log4j-changelog:jar:0.5.0 is 
invalid, transitive dependencies (if any) will not be available, enable debug 
logging for more details
exported 6 release directories: ..., `C:\tmp\test\src\changelog\0.6.0`
exporting upcoming release directory: `C:\tmp\test\src\changelog\.0.x.x`

Is that important? What doe sit mean?

TY!
Gary


On 2023/11/15 15:03:13 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j Tools 0.6.0.
> 
> Website: https://logging.staged.apache.org/log4j/tools
> GitHub: https://github.com/apache/logging-log4j-tools
> Commit: 18425d95a4d150de905929d55bf55545d70f3d91
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1233
> 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 72 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.
> 
> === Release Notes
> 
> This minor release contains various bug fixes and improvements.
> 
>  Added
> 
> * Started generating CycloneDX SBOM with the recent update of
> `logging-parent` to version `10.4.0`
> 
>  Changed
> 
> * Update `org.apache.logging:logging-parent` to version `10.4.0`
> 
>  Fixed
> 
> * `log4j-tools-bom` was broken due to removed `parent` during
> flattening. This is automatically fixed by the recent `logging-parent`
> version `10.4.0` update.
> 

Re: [VOTE] Release Apache Log4j JMX GUI 2.22.0

[Gary D. Gregory]

+1
- Testing source zip file
- OK: ASC
- OK: SHA
- OK: mvn clean verify
- OK: jar --describe-module --file=log4j-jmx-gui-2.22.0.jar

Using:

Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
Maven home: C:\java\apache-maven-3.9.5
Java version: 17.0.8, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-17.0.8.7-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Microsoft Windows [Version 10.0.19045.3570]

Gary

On 2023/11/15 15:47:17 Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j JMX GUI 2.22.0.
> 
> Website: https://logging.staged.apache.org/log4j/jmx-gui
> GitHub: https://github.com/apache/logging-log4j-jmx-gui
> Commit: a61f686edfd0d5c9591b98b80ebcfb533bebe23e
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-jmx-gui
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1234
> 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 72 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.
> 
> === Release Notes
> 
> This release contains minor improvements.
> 
> === Added
> 
> * Started generating CycloneDX SBOM with the recent update of
> `logging-parent` to version `10.4.0`
> * Publish the website[1]
> 
> [1] https://logging.apache.org/log4j/jmx-gui
> 
> === Changed
> 
> * Add OSGi and JPMS descriptors
> * Update `log4j-core` to version `2.21.1`
> * Update `logging-parent` to version `10.4.0`
> 
> === Fixed
> 
> * Restore the original Maven `groupId`: `org.apache.logging.log4j`
> 

[VOTE] Release Apache Log4j 2.22.0

[Volkan Yazıcı]

This is a vote to release the Apache Log4j 2.22.0.

Website: https://logging.staged.apache.org/log4j
GitHub: https://github.com/apache/logging-log4j2
Commit: a1634d695e5702ecab505fea5aadaf9890641487
Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j
Nexus: https://repository.apache.org/content/repositories/orgapachelogging-1238
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 72 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.

== Review kit

The minimum set of steps needed to review the uploaded distribution
files can be summarized as follows:

# Verify checksums
shasum --check *.sha512

# Verify signatures
for sigFile in *.asc; do gpg --verify $sigFile; done

# Verify reproduciblity
umask 0022
unzip *-src.zip -d src
cd src
export 
NEXUS_REPO=https://repository.apache.org/content/repositories/orgapachelogging-1238
sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO

== Release notes

This release provides a CycloneDX Software Bill of Materials (SBOM)[1]
along with each artifact and contains bug fixes addressing issues in
the JPMS & OSGi infrastructure overhauled in `2.21.0`, dependency
updates, and some other minor fixes and improvements.

[1] https://cyclonedx.org/capabilities/sbom

=== CycloneDX Software Bill of Materials (SBOM)

This is the first Log4j release that provides a CycloneDX Software
Bill of Materials (SBOM)[1] along with each artifact. Generated SBOMs
are attached as artifacts with `cyclonedx` classifier and XML
extensions, that is, `--cyclonedx.xml`. They
contain `vulnerability-assertion` references to a CycloneDX
Vulnerability Disclosure Report (VDR)[2] that Apache Logging Services
uses for all projects it maintains. This VDR is accessible through the
following URL: https://logging.apache.org/cyclonedx/vdr.xml

SBOM generation is streamlined by `logging-parent`, see its website[3]
for details.

[2] https://cyclonedx.org/capabilities/vdr
[3] https://logging.apache.org/logging-parent/latest/#cyclonedx-sbom

=== Changed

* Change the order of evaluation of `FormattedMessage` formatters.
Messages are evaluated using `java.util.Format` only if they don't
comply to the `java.text.MessageFormat` or `ParameterizedMessage`
format. (#1223)
* Change default encoding of HTTP Basic Authentication to UTF-8 and
add `log4j2.configurationAuthorizationEncoding` property to overwrite
it. (#1970)
* Update `com.fasterxml.jackson:jackson-bom` to version `2.16.0` (#1974)
* Update `com.github.luben:zstd-jni` to version `1.5.5-10` (#1940)
* Update `com.google.guava:guava` to version `32.1.3-jre` (#1875)
* Update `io.netty:netty-bom` to version `4.1.101.Final` (#1960)
* Update `org.eclipse.persistence:org.eclipse.persistence.jpa` to
version `2.7.13` (#1900)
* Update `org.fusesource.jansi:jansi` to version `2.4.1` (#1907)
* Update `org.mongodb:bson` to version `4.11.1` (#1957)
* Update `org.springframework:spring-framework-bom` to version `5.3.30`
* Update `org.springframework.boot:spring-boot` to version `2.7.17` (#1874)
* Update `org.springframework:spring-framework-bom` to version `5.3.31` (#1973)
* Update `org.zeromq:jeromq` to version `0.5.4` (#1878)

=== Removed

* Removed unused `FastDateParser` which was causing unnecessary heap
overhead (LOG4J2-3672, #1848)

=== Fixed

* Fix MDC pattern converter causing issues for `%notEmpty` (#1922)
* Export missing OSGi & JPMS modules in `log4j-layout-template-json`
and `log4j-1.2-api` (#1895)
* Fix `spring-test` dependency scope change (LOG4J2-3675)
* Fix JPMS descriptors causing `jlink` issues (#1896)
* Add missing `Implementation-` and `Specification-` entries to
`MANIFEST.MF` (implemented by `logging-parent` version `10.3.0`
update) (#1923)
* Fix `NotSerializableException` thrown when `Logger` is serialized
with a `ReusableMessageFactory` (#1884)

Re: [VOTE] Release Apache Log4j Tools 0.6.0 (RC2)

[Piotr P. Karwasz]

Hi Volkan,

On Fri, 17 Nov 2023 at 10:21, Volkan Yazıcı  wrote:
> Please download, test, and cast your votes on this mailing list.
>
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...

I have rechecked:
 * the hashes of all artifacts against locally generated ones,
 * the hashes and signatures of the ZIP archives (I believe Nexus does
it for Maven artifacts),
 * the presence of `logging-parent` in the flattened `log4j-tools-bom`,
 * the presence of CycloneDX files in the bin archive.

+1

Piotr

Re: [VOTE] Release Apache Log4j Tools 0.6.0 (RC2)

[Piotr P. Karwasz]

Hi Volkan,

On Fri, 17 Nov 2023 at 10:21, Volkan Yazıcı  wrote:
> 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.
>
> === Note on 24 hours deadline
>
> RC1 vote was created 2 days ago. RC2 only contains missing CycloneDX
> SBOMs in the distribution archived by ASF. Note that SBOMs in the
> Nexus were already working in RC1. Hence, an extra 24 hours would make
> it all add up to 72 hours.

I agree with the shorter deadline, but the vote for RC2 should not end
before the original deadline for RC1, which was:

Saturday, 18th, 15:04 UTC

This means the vote should be open for around 30 hours.

Piotr

[VOTE] Release Apache Log4j Tools 0.6.0 (RC2)

[Volkan Yazıcı]

This is a vote to release the Apache Log4j Tools 0.6.0 (RC2).

Website: https://logging.staged.apache.org/log4j/tools
GitHub: https://github.com/apache/logging-log4j-tools
Commit: a696e081304cc0693d86533013df5b4d886cfb9c
Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
Nexus: https://repository.apache.org/content/repositories/orgapachelogging-1237
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.

=== Note on 24 hours deadline

RC1 vote was created 2 days ago. RC2 only contains missing CycloneDX
SBOMs in the distribution archived by ASF. Note that SBOMs in the
Nexus were already working in RC1. Hence, an extra 24 hours would make
it all add up to 72 hours.

=== Release Notes

This minor release contains various bug fixes and improvements.

 Added

* Started generating CycloneDX SBOM with the recent update of
`logging-parent` to version `10.4.0`

 Changed

* Update `org.apache.logging:logging-parent` to version `10.4.0`

 Fixed

* `log4j-tools-bom` was broken due to removed `parent` during
flattening. This is automatically fixed by the recent `logging-parent`
version `10.4.0` update.

Re: [VOTE] Release Apache Log4j Tools 0.6.0

[Volkan Yazıcı]

Doh! As you stated [in your DM], `build.yaml` still contains the
deprecated `distribution-attachment-filepath-pattern`, which doesn't
match against SBOMs.

I am cancelling this vote.
I will issue an RC2 promptly.

On Fri, Nov 17, 2023 at 9:36 AM Piotr P. Karwasz
 wrote:
>
> Hi Volkan,
>
> On Fri, 17 Nov 2023 at 09:22, Volkan Yazıcı  wrote:
> >
> > They are. See `*-bin.zip`.
> >
> > On Fri, Nov 17, 2023 at 9:13 AM Christian Grobmeier
> >  wrote:
> > >
> > > Should the SBOM/CycloneDX files be part of the distribution folder as 
> > > well?
> > > https://dist.apache.org/repos/dist/dev/logging/log4j-tools/
>
> I can't find them either: the `log4j-jmx-gui` archive contains the
> SBOMs, but the `log4j-tools` archive doesn't.
>
> Piotr

Re: [VOTE] Release Apache Log4j Tools 0.6.0

[Piotr P. Karwasz]

Hi Volkan,

On Fri, 17 Nov 2023 at 09:22, Volkan Yazıcı  wrote:
>
> They are. See `*-bin.zip`.
>
> On Fri, Nov 17, 2023 at 9:13 AM Christian Grobmeier
>  wrote:
> >
> > Should the SBOM/CycloneDX files be part of the distribution folder as well?
> > https://dist.apache.org/repos/dist/dev/logging/log4j-tools/

I can't find them either: the `log4j-jmx-gui` archive contains the
SBOMs, but the `log4j-tools` archive doesn't.

Piotr

Re: [VOTE] Release Apache Log4j Tools 0.6.0

[Volkan Yazıcı]

They are. See `*-bin.zip`.

On Fri, Nov 17, 2023 at 9:13 AM Christian Grobmeier
 wrote:
>
> Should the SBOM/CycloneDX files be part of the distribution folder as well?
> https://dist.apache.org/repos/dist/dev/logging/log4j-tools/
>
>
> On Wed, Nov 15, 2023, at 16:03, Volkan Yazıcı wrote:
> > This is a vote to release the Apache Log4j Tools 0.6.0.
> >
> > Website: https://logging.staged.apache.org/log4j/tools
> > GitHub: https://github.com/apache/logging-log4j-tools
> > Commit: 18425d95a4d150de905929d55bf55545d70f3d91
> > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
> > Nexus: 
> > https://repository.apache.org/content/repositories/orgapachelogging-1233
> > 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 72 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.
> >
> > === Release Notes
> >
> > This minor release contains various bug fixes and improvements.
> >
> >  Added
> >
> > * Started generating CycloneDX SBOM with the recent update of
> > `logging-parent` to version `10.4.0`
> >
> >  Changed
> >
> > * Update `org.apache.logging:logging-parent` to version `10.4.0`
> >
> >  Fixed
> >
> > * `log4j-tools-bom` was broken due to removed `parent` during
> > flattening. This is automatically fixed by the recent `logging-parent`
> > version `10.4.0` update.

Re: [VOTE] Release Apache Log4j Tools 0.6.0

[Christian Grobmeier]

Should the SBOM/CycloneDX files be part of the distribution folder as well?
https://dist.apache.org/repos/dist/dev/logging/log4j-tools/


On Wed, Nov 15, 2023, at 16:03, Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j Tools 0.6.0.
>
> Website: https://logging.staged.apache.org/log4j/tools
> GitHub: https://github.com/apache/logging-log4j-tools
> Commit: 18425d95a4d150de905929d55bf55545d70f3d91
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1233
> 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 72 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.
>
> === Release Notes
>
> This minor release contains various bug fixes and improvements.
>
>  Added
>
> * Started generating CycloneDX SBOM with the recent update of
> `logging-parent` to version `10.4.0`
>
>  Changed
>
> * Update `org.apache.logging:logging-parent` to version `10.4.0`
>
>  Fixed
>
> * `log4j-tools-bom` was broken due to removed `parent` during
> flattening. This is automatically fixed by the recent `logging-parent`
> version `10.4.0` update.