Re: [VOTE] Release Apache Log4j 2.23.0 RC1

[Piotr P. Karwasz]

Hi,

On Sat, 17 Feb 2024 at 14:14, Piotr P. Karwasz  wrote:
> Please download, test, and cast your votes on this mailing list.
>
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...

And here is my +1.

The vote passes with three binding +1, from Gary, Volkan and me. I'll
continue the release process.

Piotr

Re: [VOTE] Release Apache Log4j 3.0.0-beta2 RC1

[Piotr P. Karwasz]

Hi,

On Sun, 18 Feb 2024 at 09:06, Piotr P. Karwasz  wrote:
>
> This is a vote to release the Apache Log4j 3.0.0-beta2.
>
> Website: https://logging.staged.apache.org/log4j/3.x/
> GitHub: https://github.com/apache/logging-log4j2
> Commit: 086db24a04f905b40649666aafe3bb4778a75291
> Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j
> Nexus: 
> https://repository.apache.org/content/repositories/orgapachelogging-1259
> Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0
>
> Please download, test, and cast your votes on this mailing list.
>
> [ ] +1, release the artifacts
> [ ] -1, don't release, because...

And this is my +1.

The release passes with three binding +1 from Gary, Volkan and me.
I'll continue the release process.

Piotr

Re: Clean site repo

[Piotr P. Karwasz]

Hi,

On Mon, 19 Feb 2024 at 10:34, Volkan Yazıcı  wrote:
>
> If there are no objections, after Log4j `2.23.0` and `3.0.0-beta2`
> releases, I want to proceed with replacing the contents of
> `asf-{site,staging}` branches with `clean-staging`. Effectively, this
> operation has the following outcomes:
>
>- The `logging-log4j-site` repository will contain only following files:
>   - `1.x`
>   - `2.12.x`
>   - `2.3.x`
>   - `2.x`
>   - `3.x`
>   - `.asf.yaml`
>   - `changelog-*.xsd`
>   - `extras`
>   - `.htaccess`
>- `.htaccess` will take care of redirections for backward compatibility

I have replaced `asf-staging` with `clean-staging`, but `asf-site`
remains for now untouched.

Please peruse the `https://logging.staged.apache.org/log4j/` pages to
see if something is wrong.

As I stated before, the main rationale behind this change is SEO. What
do you get if you perform the following search:

https://www.google.com/search?client=firefox-b-e&q=DefaultThreadContextMap+log4j+javadoc

The result depends on the location, but I find results from:

 * /log4j/2.0/: (sic!) I didn't even know it existed, can someone tell
me from which repo is this served?
 * /log4j/log4j-2.3.2/
 * Eventually there is a result from `/log4j/2.x/` but pointing at the
wrong class.

Remark: in the renewed staging site there are **still** a
/log4j/2.3.x/ and /log4j/2.12.x/ folders and the rewrite rules
"round-up" the `/log4j/log4j-` folders to one of
/log4j/2.3.x/, `/log4j/2.12.x/` or `/log4j/2.x/`.
We could probably also drop the documentation of those versions too,
but this is another discussion.

Piotr

PS: right now INFRA didn't update
https://logging.staged.apache.org/log4j/ yet, but you can see the
intended content on https://logging-clean.staged.apache.org/log4j/

[ANNOUNCE] Apache Log4j 3.0.0-beta2 released

[Piotr P. Karwasz]

The Apache Log4j team is pleased to announce the 3.0.0-beta2
release. Apache Log4j is a versatile, industrial-strength
Java logging framework composed of an API, its implementation,
and components to assist the deployment for various use cases.
For further information (support, download, etc.) see the project
website[1].

[1] https://logging.apache.org/log4j/3.x/

== Release Notes

This release provides a continuation of the modularisation process of
Log4j Core.

The following features were moved to separate artifacts:

* The async logger feature was moved to `log4j-async-logger` and it
was upgraded to use LMAX Disruptor 4.x.
The async appender is still available by default in `log4j-core`.
* The YAML configuration is available now in `log4j-config-yaml`.
* The Java properties configuration was removed and replaced with a
similar format based on `jackson-dataformat-properties` in a new

`log4j-config-properties` artifact.


Other features were removed:

* Jetty 9.x users are encouraged to migrate to Jetty 10.x or later and
replace `log4j-appserver` with `log4j-slf4j2-impl`.
* Tomcat JULI support will be available from a third-party (cf.
https://github.com/copernik-eu/log4j-plugins 
).

* Apache Commons Logging users are encouraged to upgrade
`commons-logging` to version 1.3.0 or later and remove `log4j-jcl`.
* Support for the XML layout was dropped.
* Support for JMX was dropped and will be replaced with a more recent
technology.

=== Added

* Add and update DSLs for setting up dependency injection for test and
non-test code. (#2147)
* Add a `ConfigurationExtension` mechanism to allow third-party JARs
to extend the `` element.
* Add a new properties configuration factory based on
`jackson-dataformat-properties`.

=== 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)
* Split off async logger support into a new `log4j-async-logger` module.
* Split off YAML configuration into a new `log4j-config-yaml` module.

=== Fixed

* Rewrote message parameter formatter with improved escape handling (#1626)
* The MongoDb4 appender now supports long values to configure
`collectionSize` (#1747)
* Mark `JdkMapAdapterStringMap` as frozen if map is immutable. (#2098)
* Fix regression in `JdkMapAdapterStringMap` performance. (#2238)
* Prevents ClassCastException when trying to assign a
SimpleLoggerContext to a core LoggerContext (LOG4J2-1921)
* Possible NullPointerException in MongoDb4DocumentObject,
MongoDbDocumentObject, DefaultNoSqlObject. (LOG4J2-3392)
* Fix NPE in `CloseableThreadContext`. (#1426)
* Fix NPE in `RollingFileManager`. (#1645)
* Fix `log4j-spring-cloud-config-client` dependencies to include only
those required. (2157)
* Workaround a Coursier/Ivy dependency resolution bug affecting
`log4j-slf4j-impl` and `log4j-mongodb3`. (#2065)

=== Removed

* Removed legacy `2.x` properties configuration factory.
* Remove `DefaultLogEventFactory`
* Remove `log4j-appserver` module (#2257)
* Remove `org.apache.logging.log4j.core.parser` and related packages. 
(#2154)

* Remove `log4j-jcl` module (#2257)
* Removed JMX support.
* Remove `log4j-layout-jackson` module (#2198)
* Remove `log4j-layout-jackson-xml` module (#2198)
* Remove `log4j2.enable.threadlocals` property (#2105)

=== Updated

* Update `com.fasterxml.jackson:jackson-bom` to version `2.16.1` (#2127)
* Update `commons-codec:commons-codec` to version `1.16.1` (#2276)
* Update `io.netty:netty-bom` to version `4.1.107.Final` (#2283)
* Update `org.apache.logging:logging-parent` to version `10.6.0` (#2193)
* Update `org.apache.tomcat:tomcat-juli` to version `10.1.18` (#2176)
* Update `org.eclipse.jetty:jetty-bom` to version `9.4.54.v20240208` (#2285)
* Update `org.jctools:jctools-core` to version `4.0.3` (#2267)
* Update `org.slf4j:slf4j-api` to version `2.0.10` (#2136)
* Update `org.springframework.boot:spring-boot-autoconfigure` to
version `3.2.2` (#)
* Update `org.springframework.cloud:spring-cloud-context` to version
`4.1.1` (#2236)
* Update `org.springframework:spring-framework-bom` to version `6.1.4` 
(#2294)

[ANNOUNCE] Apache Log4j 2.23.0 released

[Piotr P. Karwasz]

The Apache Log4j team is pleased to announce the 2.23.0
release. Apache Log4j is a versatile, industrial-strength
Java logging framework composed of an API, its implementation,
and components to assist the deployment for various use cases.
For further information (support, download, etc.) see the project
website[1].

[1] https://logging.apache.org/log4j/2.x/

== Release Notes

This release adds support for LMAX Disruptor 4.x and several
performance and bug fixes.

In order to maintain compatibility with JRE 8, support for LMAX
Disruptor 3.x is maintained.

=== Added

* Added support for LMAX Disruptor 4.x (#1821)

=== Changed

* Simplify BND configuration after upgrade from version `6.4.1` to `7.0.0`

=== Deprecated

* Deprecate the configuration attribute `verbose` (i.e.,
` node to appear in any position in the
configuration element.
* Fix forgotten `threadName` field in `RingBufferLogEvent#clear()` (#2234)
* Fix `StringBuilder` cache corruption on recursive access
* Fixed use of `SecurityManager` in `LoaderUtil` where
`AccessController::doPrivilege

d` should only be invoked when a
`SecurityManager` is installed. Some runtimes do not seem to have this
method available. (#2129)
* Fix `log4j-spring-cloud-config-client` dependencies to include only
those required. (#2157)
* Fix typo in Kubernetes `clientKeyData` configuration property.

=== Updated

* Update `com.fasterxml.jackson:jackson-bom` to version `2.16.1` (#2126)
* Update `commons-codec:commons-codec` to version `1.16.1` (#2277)
* Update `io.netty:netty-bom` to version `4.1.107.Final` (#2284)
* Update `org.apache.logging:logging-parent` to version `10.6.0` (#2197)
* Update `org.eclipse.jetty:jetty-bom` to version `9.4.54.v20240208` (#2287)
* Update `org.jctools:jctools-core` to version `4.0.3` (#2270)
* Update `org.springframework:spring-framework-bom` to version `5.3.32` 
(#2293)

* Update `org.zeromq:jeromq` to version `0.6.0` (#2271)