Re: Dist directories

2022-09-11 Thread Gary Gregory
I am asking because that directory is the link provided in the vote and we
vote on sources.

Gary

On Sat, Sep 10, 2022, 17:51 Ralph Goers  wrote:

> I am not sure why you asked this in the vote thread.
>
> It is empty because that is where the Kotlin releases would go while
> they are voted on and there is no vote open. That would mean they
> were moved to the release directory. Sometimes the artifacts are
> copied and then deleted when the next release comes along.
>
> Ralph
>
> > On Sep 10, 2022, at 4:29 PM, Gary Gregory 
> wrote:
> >
> > Is the directory
> > https://dist.apache.org/repos/dist/dev/logging/log4j/kotlin/ empty on
> > purpose?
> >
> > Gary
> >
>
>


Re: [VOTE] Release Apache Log4j 2.19.0-rc1

2022-09-11 Thread Boris Unckel
+1

Tested against
* WildFly Core main with -DallTests ( https://github.com/wildfly/wildfly-core/ )
* JBoss Logging 3.4 branch ( 
https://github.com/jboss-logging/jboss-logging/tree/3.4 )
* Log4j2 JBoss Logmanager main( 
https://github.com/jboss-logging/log4j2-jboss-logmanager )

Regards
Boris

> Ralph Goers  hat am 10.09.2022 00:56 CEST 
> geschrieben:
> 
>  
> This is a vote to release Log4j 2.19.0, the next version of the Log4j 2 
> project.
> 
> Note that the security page on the web site was updated to better describe 
> CVE-2021-44228 and CVE-2021-45046. Please review those changes.
> 
> 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.


Re: [VOTE] Release Apache Log4j 2.19.0-rc1

2022-09-11 Thread Matt Sicker
Gary, the `kotlin` directory is for placing release candidates for the Log4j 
Kotlin API. Same with the `scala` directory there. Whenever I promote a release 
candidate to a release, I use `svn mv` between dist/dev to dist/prod basically. 
See step (13) in 
https://cwiki.apache.org/confluence/display/LOGGING/Log4j+Kotlin+API+Release+Process
 

 for how exactly that’s done.
—
Matt Sicker

> On Sep 10, 2022, at 18:29, Gary Gregory  wrote:
> 
> Is the directory
> https://dist.apache.org/repos/dist/dev/logging/log4j/kotlin/ empty on
> purpose?
> 
> Gary
> 
> On Fri, Sep 9, 2022, 15:56 Ralph Goers  wrote:
> 
>> This is a vote to release Log4j 2.19.0, the next version of the Log4j 2
>> project.
>> 
>> Note that the security page on the web site was updated to better describe
>> CVE-2021-44228 and CVE-2021-45046. Please review those changes.
>> 
>> 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.
>> 
>> Changes in this version include:
>> 
>> New Features
>>• LOG4J2-3583: Add support for SLF4J2 stack-valued MDC. Thanks to
>> Pierrick Terrettaz.
>>• LOG4J2-2975: Add implementation of SLF4J2 fluent API. Thanks to
>> Daniel Gray.
>> Fixed Bugs
>>• LOG4J2-3578: Generate new SSL certs for testing.
>>• LOG4J2-3556: Make JsonTemplateLayout stack trace truncation
>> operate for each label block. Thanks to Arthur Gavlyukovskiy.
>>• LOG4J2-3550: SystemPropertyArbiter was assigning the value as
>> the name. Thanks to DongjianPeng.
>>• LOG4J2-3560: Logger$PrivateConfig.filter(Level, Marker, String)
>> was allocating empty varargs array. Thanks to David Schlosnagle.
>>• LOG4J2-3561: Allows a space separated list of style specifiers
>> in the %style pattern for consistency with %highlight. Thanks to Robert
>> Papp.
>>• LOG4J2-3564: Fix NPE in log4j-to-jul in the case the root logger
>> level is null.
>>• LOG4J2-3545: Add correct manifest entries for OSGi to log4j-jcl
>> Thanks to Johan Compagner.
>>• LOG4J2-3565: Fix RollingRandomAccessFileAppender with
>> DirectWriteRolloverStrategy can't create the first log file of different
>> directory.
>>• LOG4J2-3579: Fix ServiceLoaderUtil behavior in the presence of a
>> SecurityManager. Thanks to Boris Unckel.
>>• LOG4J2-3559: Fix resolution of properties not starting with
>> log4j2.. Thanks to Gary Gregory.
>>• LOG4J2-3557: Fix recursion between Log4j 1.2 LogManager and
>> Category. Thanks to Andreas Leitgeb.
>>• LOG4J2-3587: Fix regression in Rfc5424Layout default values.
>> Thanks to Tomas Micko.
>>• LOG4J2-3548: Improve support for passwordless keystores. Thanks
>> to Kristof Farkas-Pall.
>> Changes
>>• LOG4J2-3572: Add getExlicitLevel method to LoggerConfig.
>>• LOG4J2-3589: Allow Plugins to be injected with the LoggerContext
>> reference.
>>• LOG4J2-3588: Allow PropertySources to be added.
>> Removed
>>• LOG4J2-3573: Removed build page in favor of a single build
>> instructions file. Thanks to Wolff Bock von Wuelfingen.
>>• LOG4J2-3590: Remove SLF4J 1.8.x binding.
>> 
>> Tag:
>> a)  for a new copy do "git clone
>> https://github.com/apache/logging-log4j2.git and then "git checkout
>> tags/log4j-2.19.0-rc1”  or just "git clone -b log4j-2.19.0-rc1
>> https://github.com/apache/logging-log4j2.git";
>> b) for an existing working copy to “git pull” and then “git checkout
>> tags/log4j-2.19.0-rc1”
>> 
>> Web Site:  https://logging.staged.apache.org/log4j/2.x/index.html.
>> 
>> Maven Artifacts:
>> https://repository.apache.org/content/repositories/orgapachelogging-1088/
>> 
>> Distribution archives:
>> https://dist.apache.org/repos/dist/dev/logging/log4j/
>> 
>> You may download all the Maven artifacts by executing:
>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>> https://repository.apache.org/content/repositories/orgapachelogging-1088/org/apache/logging/log4j/
>> 
>> Ralph



Re: [VOTE] Release Apache Log4j 2.19.0-rc1

2022-09-11 Thread Matt Sicker
+1


Tested on combination of:

openjdk version "1.8.0_322"
OpenJDK Runtime Environment (Zulu 8.60.0.21-CA-macos-aarch64) (build 
1.8.0_322-b06)
OpenJDK 64-Bit Server VM (Zulu 8.60.0.21-CA-macos-aarch64) (build 25.322-b06, 
mixed mode)

openjdk version "11.0.15" 2022-04-19 LTS
OpenJDK Runtime Environment Zulu11.56+19-CA (build 11.0.15+10-LTS)
OpenJDK 64-Bit Server VM Zulu11.56+19-CA (build 11.0.15+10-LTS, mixed mode)

—
Matt Sicker

> On Sep 9, 2022, at 17:56, Ralph Goers  wrote:
> 
> This is a vote to release Log4j 2.19.0, the next version of the Log4j 2 
> project.
> 
> Note that the security page on the web site was updated to better describe 
> CVE-2021-44228 and CVE-2021-45046. Please review those changes.
> 
> 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.
> 
> Changes in this version include:
> 
> New Features
>   • LOG4J2-3583: Add support for SLF4J2 stack-valued MDC. Thanks to 
> Pierrick Terrettaz.
>   • LOG4J2-2975: Add implementation of SLF4J2 fluent API. Thanks to 
> Daniel Gray.
> Fixed Bugs
>   • LOG4J2-3578: Generate new SSL certs for testing.
>   • LOG4J2-3556: Make JsonTemplateLayout stack trace truncation operate 
> for each label block. Thanks to Arthur Gavlyukovskiy.
>   • LOG4J2-3550: SystemPropertyArbiter was assigning the value as the 
> name. Thanks to DongjianPeng.
>   • LOG4J2-3560: Logger$PrivateConfig.filter(Level, Marker, String) was 
> allocating empty varargs array. Thanks to David Schlosnagle.
>   • LOG4J2-3561: Allows a space separated list of style specifiers in the 
> %style pattern for consistency with %highlight. Thanks to Robert Papp.
>   • LOG4J2-3564: Fix NPE in log4j-to-jul in the case the root logger 
> level is null.
>   • LOG4J2-3545: Add correct manifest entries for OSGi to log4j-jcl 
> Thanks to Johan Compagner.
>   • LOG4J2-3565: Fix RollingRandomAccessFileAppender with 
> DirectWriteRolloverStrategy can't create the first log file of different 
> directory.
>   • LOG4J2-3579: Fix ServiceLoaderUtil behavior in the presence of a 
> SecurityManager. Thanks to Boris Unckel.
>   • LOG4J2-3559: Fix resolution of properties not starting with log4j2.. 
> Thanks to Gary Gregory.
>   • LOG4J2-3557: Fix recursion between Log4j 1.2 LogManager and Category. 
> Thanks to Andreas Leitgeb.
>   • LOG4J2-3587: Fix regression in Rfc5424Layout default values. Thanks 
> to Tomas Micko.
>   • LOG4J2-3548: Improve support for passwordless keystores. Thanks to 
> Kristof Farkas-Pall.
> Changes
>   • LOG4J2-3572: Add getExlicitLevel method to LoggerConfig.
>   • LOG4J2-3589: Allow Plugins to be injected with the LoggerContext 
> reference.
>   • LOG4J2-3588: Allow PropertySources to be added.
> Removed
>   • LOG4J2-3573: Removed build page in favor of a single build 
> instructions file. Thanks to Wolff Bock von Wuelfingen.
>   • LOG4J2-3590: Remove SLF4J 1.8.x binding.
> 
> Tag: 
> a)  for a new copy do "git clone https://github.com/apache/logging-log4j2.git 
> and then "git checkout tags/log4j-2.19.0-rc1”  or just "git clone -b 
> log4j-2.19.0-rc1 https://github.com/apache/logging-log4j2.git";
> b) for an existing working copy to “git pull” and then “git checkout 
> tags/log4j-2.19.0-rc1”
> 
> Web Site:  https://logging.staged.apache.org/log4j/2.x/index.html.
> 
> Maven Artifacts: 
> https://repository.apache.org/content/repositories/orgapachelogging-1088/
> 
> Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j/ 
> 
> You may download all the Maven artifacts by executing:
> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate 
> https://repository.apache.org/content/repositories/orgapachelogging-1088/org/apache/logging/log4j/
> 
> Ralph



Re: Structured concurrency in Java 19+

2022-09-11 Thread Matt Sicker
Scoped variables are a great example! There’s a similar concept in some 
reactive streams APIs (which is also a standard Java API starting in 9) with 
“contexts”, and the same concept is also available in the standard Go library 
in its “context” package for associating arbitrary values with string keys.
—
Matt Sicker

> On Sep 9, 2022, at 02:00, Volkan Yazıcı  wrote:
> 
> I expect scoped variables that will be introduced with Loom to replace MDC
> attached to threads.
> 
> On Wed, Sep 7, 2022 at 8:41 PM Matt Sicker  wrote:
> 
>> Java 19 is coming out soon, and that includes a preview version of virtual
>> threads and structured concurrency APIs. While I’m not that familiar with
>> the Java implementation, I’d imagine it’ll have some similarities with
>> Kotlin coroutines and other similar structured concurrency libraries.
>> 
>> I’ve played around with the general concept myself, particularly an
>> interesting Python library for the same. I think some sort of structured
>> concurrency architecture would be useful for making some async aspects of
>> Log4j easier to understand (mostly the areas where we spawn threads for
>> things, not for async logging). While the API isn’t stable, we can abstract
>> it well enough with multi version jars. What I’m more curious about is how
>> we’d interact (if at all) with virtual threads, coroutines, or structured
>> concurrency APIs in general. If an app uses structured concurrency
>> throughout, it might want the logging system to participate in the same
>> flow for clean shutdowns.
>> 
>> Does anyone have any more concrete use cases that might be relevant for
>> us? Or does this seem more relevant for networking libraries and frameworks?
>> 
>> —
>> Matt Sicker



Re: [VOTE] Release Apache Log4j 2.19.0-rc1

2022-09-11 Thread Ron Grabowski
I saw the same errors with JDK8 on Windows:

openjdk version "1.8.0_342"
OpenJDK Runtime Environment Corretto-8.342.07.3 (build 1.8.0_342-b07)
OpenJDK 64-Bit Server VM Corretto-8.342.07.3 (build 25.342-b07, mixed mode)

[ERROR] Errors:
[ERROR]   
GelfLayoutTest.testLayoutNewLineDelimiter:286->testCompressedLayout:189 ▒ 
IndexOutOfBounds Index: 2, Size: 2
[ERROR]   GelfLayoutTest.testLayoutNoCompression:256->testCompressedLayout:189 
▒ IndexOutOfBounds Index: 2, Size: 2
[ERROR]   GelfLayoutTest.testLayoutNoHost:276->testCompressedLayout:189 ▒ 
IndexOutOfBounds Index: 2, Size: 2
[ERROR]   
GelfLayoutTest.testLayoutNoThreadContext:271->testCompressedLayout:189 ▒ 
IndexOutOfBounds Index: 2, Size: 2
[INFO]
[ERROR] Tests run: 2405, Failures: 0, Errors: 4, Skipped: 13

Different error with JDK11 on Windows:

openjdk version "11.0.16.1" 2022-08-12 LTS
OpenJDK Runtime Environment Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS)
OpenJDK 64-Bit Server VM Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS, mixed 
mode)

[ERROR] 
log4j-2.19.0-rc1\log4j-api\src\test\java\org\apache\logging\log4j\util\StackLocatorUtilTest.java:[31,18]
 error: cannot find symbol
[ERROR]   symbol:   class Reflection
[ERROR]   location: package sun.reflect

On 2022/09/11 16:12:51 Gary Gregory wrote:
> I am away from home and my mac, so I am testing on Windows where I always
> get these failures:
> 
> 
> [INFO]
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running org.apache.logging.log4j.core.layout.GelfLayoutTest
> ERROR StatusLogger Recovering from
> StringBuilderEncoder.encode('{"version":"1.1","host":"US-L-GG02","timestamp":1662912585.090,"level":3,"_thread":"main","_logger":"","_Key1":"Value1","_Key2":"OpenJDK
> Runtime Environment (build 1.8.0_342-b07) from
> Temurin","_MdcKey1":"MdcValue1","_MdcKey2":"MdcValue2","full_message":"java.lang.RuntimeException:
> some error\r\n\tat
> org.apache.logging.log4j.core.layout.GelfLayoutTest.testCompressedLayout(GelfLayoutTest.java:135)\r\n\tat
> org.apache.logging.log4j.core.layout.GelfLayoutTest.testLayoutNoHost(GelfLayoutTest.java:276)\r\n\tat

[snip]

> 
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR]
>  GelfLayoutTest.testLayoutNewLineDelimiter:286->testCompressedLayout:189 »
> IndexOutOfBounds Index: 2, Size: 2
> [ERROR]
>  GelfLayoutTest.testLayoutNoCompression:256->testCompressedLayout:189 »
> IndexOutOfBounds Index: 2, Size: 2
> [ERROR]   GelfLayoutTest.testLayoutNoHost:276->testCompressedLayout:189 »
> IndexOutOfBounds Index: 2, Size: 2
> [ERROR]
>  GelfLayoutTest.testLayoutNoThreadContext:271->testCompressedLayout:189 »
> IndexOutOfBounds Index: 2, Size: 2
> [INFO]
> [ERROR] Tests run: 12, Failures: 0, Errors: 4, Skipped: 0
> [INFO]
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time:  16.182 s
> [INFO] Finished at: 2022-09-11T09:09:46-07:00
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (default-test)
> on project log4j-core:
> [ERROR]
> [ERROR] Please refer to
> C:\temp\apache-log4j-2.19.0-src\log4j-core\target\surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump,
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> 
> Thoughts?
> 
> Gary
> 
> On Fri, Sep 9, 2022, 15:56 Ralph Goers  wrote:
> 
> > This is a vote to release Log4j 2.19.0, the next version of the Log4j 2
> > project.
> >
> > Note that the security page on the web site was updated to better describe
> > CVE-2021-44228 and CVE-2021-45046. Please review those changes.
> >
> > 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.
> >
> > Changes in this version include:
> >
> > New Features
> > • LOG4J2-3583: Add support for SLF4J2 stack-valued MDC. Thanks to
> > Pierrick Terrettaz.
> > • LOG4J2-2975: Add implementation of SLF4J2 fluent API. Thanks to
> > Daniel Gray.
> > Fixed Bugs
> > • LOG4J2-357

Re: [VOTE] Release Apache Log4j 2.19.0-rc1

2022-09-11 Thread Piotr P. Karwasz
Hi Gary,

On Sun, 11 Sept 2022 at 18:13, Gary Gregory  wrote:
>
>  java.lang.IllegalStateException: Unexpected message larger than 4096 bytes

This is probably due to the 8192 bytes limit in
`EncodingListAppender.Destination`. We should probably increase it.

Piotr


Re: [VOTE] Release Apache Log4j 2.19.0-rc1

2022-09-11 Thread Matt Sicker
I get the same error when running on java 11, too, but that’s to be expected. I 
wrote that test originally to explicitly detect the point at which we’d have to 
do something about it, and we already addressed the original issue long ago. In 
the 2.x branch, this is handled by using Maven toolchains for switching from 
java 8. In the 3.x branch, this test was updated to avoid referencing outdated 
internal APIs due to the base java version requirements there.

—
Matt Sicker

> On Sep 11, 2022, at 16:01, Ron Grabowski  wrote:
> 
> I saw the same errors with JDK8 on Windows:
> 
> openjdk version "1.8.0_342"
> OpenJDK Runtime Environment Corretto-8.342.07.3 (build 1.8.0_342-b07)
> OpenJDK 64-Bit Server VM Corretto-8.342.07.3 (build 25.342-b07, mixed mode)
> 
> [ERROR] Errors:
> [ERROR]   
> GelfLayoutTest.testLayoutNewLineDelimiter:286->testCompressedLayout:189 ▒ 
> IndexOutOfBounds Index: 2, Size: 2
> [ERROR]   
> GelfLayoutTest.testLayoutNoCompression:256->testCompressedLayout:189 ▒ 
> IndexOutOfBounds Index: 2, Size: 2
> [ERROR]   GelfLayoutTest.testLayoutNoHost:276->testCompressedLayout:189 ▒ 
> IndexOutOfBounds Index: 2, Size: 2
> [ERROR]   
> GelfLayoutTest.testLayoutNoThreadContext:271->testCompressedLayout:189 ▒ 
> IndexOutOfBounds Index: 2, Size: 2
> [INFO]
> [ERROR] Tests run: 2405, Failures: 0, Errors: 4, Skipped: 13
> 
> Different error with JDK11 on Windows:
> 
> openjdk version "11.0.16.1" 2022-08-12 LTS
> OpenJDK Runtime Environment Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS)
> OpenJDK 64-Bit Server VM Corretto-11.0.16.9.1 (build 11.0.16.1+9-LTS, mixed 
> mode)
> 
> [ERROR] 
> log4j-2.19.0-rc1\log4j-api\src\test\java\org\apache\logging\log4j\util\StackLocatorUtilTest.java:[31,18]
>  error: cannot find symbol
> [ERROR]   symbol:   class Reflection
> [ERROR]   location: package sun.reflect
> 
>> On 2022/09/11 16:12:51 Gary Gregory wrote:
>> I am away from home and my mac, so I am testing on Windows where I always
>> get these failures:
>> 
>> 
>> [INFO]
>> [INFO] ---
>> [INFO]  T E S T S
>> [INFO] ---
>> [INFO] Running org.apache.logging.log4j.core.layout.GelfLayoutTest
>> ERROR StatusLogger Recovering from
>> StringBuilderEncoder.encode('{"version":"1.1","host":"US-L-GG02","timestamp":1662912585.090,"level":3,"_thread":"main","_logger":"","_Key1":"Value1","_Key2":"OpenJDK
>> Runtime Environment (build 1.8.0_342-b07) from
>> Temurin","_MdcKey1":"MdcValue1","_MdcKey2":"MdcValue2","full_message":"java.lang.RuntimeException:
>> some error\r\n\tat
>> org.apache.logging.log4j.core.layout.GelfLayoutTest.testCompressedLayout(GelfLayoutTest.java:135)\r\n\tat
>> org.apache.logging.log4j.core.layout.GelfLayoutTest.testLayoutNoHost(GelfLayoutTest.java:276)\r\n\tat
> 
> [snip]
> 
>> 
>> [INFO]
>> [INFO] Results:
>> [INFO]
>> [ERROR] Errors:
>> [ERROR]
>> GelfLayoutTest.testLayoutNewLineDelimiter:286->testCompressedLayout:189 »
>> IndexOutOfBounds Index: 2, Size: 2
>> [ERROR]
>> GelfLayoutTest.testLayoutNoCompression:256->testCompressedLayout:189 »
>> IndexOutOfBounds Index: 2, Size: 2
>> [ERROR]   GelfLayoutTest.testLayoutNoHost:276->testCompressedLayout:189 »
>> IndexOutOfBounds Index: 2, Size: 2
>> [ERROR]
>> GelfLayoutTest.testLayoutNoThreadContext:271->testCompressedLayout:189 »
>> IndexOutOfBounds Index: 2, Size: 2
>> [INFO]
>> [ERROR] Tests run: 12, Failures: 0, Errors: 4, Skipped: 0
>> [INFO]
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time:  16.182 s
>> [INFO] Finished at: 2022-09-11T09:09:46-07:00
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (default-test)
>> on project log4j-core:
>> [ERROR]
>> [ERROR] Please refer to
>> C:\temp\apache-log4j-2.19.0-src\log4j-core\target\surefire-reports for the
>> individual test results.
>> [ERROR] Please refer to dump files (if any exist) [date].dump,
>> [date]-jvmRun[N].dump and [date].dumpstream.
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
>> switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>> 
>> Thoughts?
>> 
>> Gary
>> 
>>> On Fri, Sep 9, 2022, 15:56 Ralph Goers  wrote:
>>> 
>>> This is a vote to release Log4j 2.19.0, the next version of the Log4j 2
>>> project.
>>> 
>>> Note that the security page on the web site was updated to better describe
>>> CVE-2021-44228 and CVE-2021-45046. Please review those changes.
>>> 
>>> Please download, test