The Apache Log4j 2 team is pleased to announce the Log4j 2.18.0 release!
Apache Log4j is a well known framework for logging application behavior. Log4j
2 is an upgrade to Log4j that provides significant improvements over its
predecessor, Log4j 1.x, and provides many other modern features
This vote has passed with +1 votes from Matt Sicker, Remko Popma, and Ralph
Goers. I will continue with the release process.
Ralph
at
>> org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:67)
>>>>> at
>> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:52)
>>>>> at
>
te(LazyLauncher.java:55)
> > >> at
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.execute(JUnitPlatformProvider.java:223)
> > >> at
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.invokeAllTests(JUnitPlatformProvider.java:175)
.maven.surefire.junitplatform.LazyLauncher.execute(LazyLauncher.java:55)
> >> at
> >> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.execute(JUnitPlatformProvider.java:223)
> >> at
> >> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.inv
+1
Sigs good, build and test good, site looks fine.
—
Matt Sicker
> On Jun 28, 2022, at 19:00, Ralph Goers wrote:
>
> This is a vote to release Log4j 2.18.0, the next version of the Log4j 2
> project.
>
> Please download, test, and cast your votes on the log4j develo
t;> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.invoke(JUnitPlatformProvider.java:135)
>> at
>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:456)
>> at
>> org.apache.maven.surefire.booter.ForkedBooter.execute(Fork
n verify
>
> on
>
> Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> Maven home: /usr/local/Cellar/maven/3.8.6/libexec
> Java version: 1.8.0_322, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@8/1.8.0+322/libexec/openjdk.jdk/Contents/Home/jre
> Def
: "x86_64", family: "mac"
Anyone else?
Gary
On Tue, Jun 28, 2022 at 8:00 PM Ralph Goers wrote:
>
> This is a vote to release Log4j 2.18.0, the next version of the Log4j 2
> project.
>
> Please download, test, and cast your votes on the log4j devel
This is a vote to release Log4j 2.18.0, the next version of the Log4j 2 project.
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
Hi Ralph,
On Mon, 27 Jun 2022 at 17:36, Ralph Goers wrote:
> I have no problem upgrading the JEE stuff like all the other dependencies
> except when it switches from javax to Jakarta.
Of course, I upgraded to the last version using the `javax.*` namespace.
Piotr
I have no problem upgrading the JEE stuff like all the other dependencies
except when it switches from javax to Jakarta.
Ralph
> On Jun 26, 2022, at 11:30 PM, Piotr P. Karwasz
> wrote:
>
> Hi Ralph,
>
> On Mon, 27 Jun 2022 at 07:52, Ralph Goers wrote:
>> Note that I don’t usually create a
Hi Ralph,
On Mon, 27 Jun 2022 at 07:52, Ralph Goers wrote:
> Note that I don’t usually create a release branch. Things have been pretty
> quiet of late so I don’t plan to for this one either. So if you are going to
> commit something that will require me to start over please let me know so I
I have fixed the last bug I was targeting for 2.18.0. So I am not going to be
going through my release process. The first step is running the web site build
at which time I will address LOG4J2-3510.
It usually takes me a couple of days to get a release candidate ready.
Note that I don’t
Hi Ralph,
On Mon, 30 May 2022 at 09:11, Ralph Goers
wrote:
> I ran it multiple times in my Windows VM and it failed each time. I am not
> going
> to hunt down what directories I need to be deleting. The test needs to do
> that.
>
I perfectly understand your POV. Actually looking at the test's
I ran it multiple times in my Windows VM and it failed each time. I am not
going
to hunt down what directories I need to be deleting. The test needs to do that.
Since H2 is only used for testing I don’t consider it a big deal. The link you
provided clearly shows it is a test dependency so
Hi Ralph,
On Mon, 30 May 2022 at 00:26, Ralph Goers
wrote:
> FWIW, the h2 upgrade broke the build. I am in the process of reverting the
> version change.
>
> Ralph
>
I would really like the H2 upgrade to be included in 2.18.0, so that pages
like this:
FWIW, the h2 upgrade broke the build. I am in the process of reverting the
version change.
Ralph
> On May 25, 2022, at 10:30 PM, Piotr P. Karwasz
> wrote:
>
> Hi Ralph,
>
> On Thu, 26 May 2022 at 06:47, Ralph Goers
> wrote:
>
>> If you are confident in it then feel free to commit it.
Hi Ralph,
On Thu, 26 May 2022 at 06:47, Ralph Goers
wrote:
> If you are confident in it then feel free to commit it. Remember, we still
> fundamentally
> operate using CTR so even if you are using PRs you don’t necessarily have
> to wait
> for approvals. That said, I glanced at the PR and
Hi Ralph,
On Wed, 25 May 2022 at 05:44, Ralph Goers
wrote:
> I’ve created https://issues.apache.org/jira/browse/LOG4J2-3516 for this.
>
> Ralph
>
Thanks for the fix.
In the meantime I solved the small obstacle to the H2 upgrade (
https://github.com/eclipse-ee4j/eclipselink/issues/1393), so
I’ve created https://issues.apache.org/jira/browse/LOG4J2-3516 for this.
Ralph
> On May 24, 2022, at 9:41 PM, Ralph Goers wrote:
>
>
>
>> On May 24, 2022, at 2:25 PM, Piotr P. Karwasz
>> wrote:
>>
>> The 'log4j:log4j' dependency is only used in some performance tests, which
>> probably
> On May 24, 2022, at 2:25 PM, Piotr P. Karwasz wrote:
>
> The 'log4j:log4j' dependency is only used in some performance tests, which
> probably should move to `log4j-perf`:
> https://github.com/apache/logging-log4j2/pull/890.
> If we also upgrade `h2` the `log4j-api` and `log4j-core`
Hi Volkan,
On Tue, 24 May 2022 at 20:41, Volkan Yazıcı wrote:
> That is a spot on remark with security updates, in particular
> Jackson-related ones, Piotr. Yes, we shouldn't indeed ship 2.18.0 without
> the Jackson updates. I presume you are already taking care of this?
>
Yes, Jackson is
That is a spot on remark with security updates, in particular
Jackson-related ones, Piotr. Yes, we shouldn't indeed ship 2.18.0 without
the Jackson updates. I presume you are already taking care of this?
> Removing the `log4j` 1.x dependency from `log4j-core`
What do you exactly mean?
Hi Ralph,
On Fri, 20 May 2022 at 18:06, Ralph Goers
wrote:
> I am working through the last few issues I want to resolve for 2.18.0.
> I’d like to hope I can have them done today but I might not. I will be
> traveling tomorrow through Wed, May 25 to visit friends and family. While
> it is
Sounds good to me. I'll see if I have anything pending over the weekend but
if I do it is not critical.
Gary
On Fri, May 20, 2022, 12:06 Ralph Goers wrote:
> I am working through the last few issues I want to resolve for 2.18.0.
> I’d like to hope I can have them done today but I might not. I
I am working through the last few issues I want to resolve for 2.18.0. I’d
like to hope I can have them done today but I might not. I will be traveling
tomorrow through Wed, May 25 to visit friends and family. While it is possible
I might be able to do the release then, it is unlikely. So
27 matches
Mail list logo
