Re: [VOTE][LAZY] Release Apache Logging Parent `11.0.0`

2024-04-18 Thread Volkan Yazıcı 
Adding my +1.

With that, the release passes with 1 binding +1 vote from me. I will
continue the release process.

On Mon, Apr 15, 2024 at 1:11 PM Volkan Yazıcı  wrote:

> This is a lazy-vote to release the Apache Logging Parent `11.0.0`.
>
> Website: https://logging.staged.apache.org/logging-parent-11.0.0
> GitHub: https://github.com/apache/logging-parent
> Commit: b5bbe45c0c3536e3b6532e176e038a166310df16
> Distribution:
> https://dist.apache.org/repos/dist/dev/logging/logging-parent
> Nexus:
> https://repository.apache.org/content/repositories/orgapachelogging-1281
> 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 in the Subversion repository can be summarized as follows:
>
> # Check out the distribution
> svn co
> https://dist.apache.org/repos/dist/dev/logging/logging-parent/11.0.0 &&
> cd $_
>
> # Verify checksums
> shasum --check *.sha512
>
> # Verify signatures
> wget -O - https://downloads.apache.org/logging/KEYS | gpg --import
> 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-1281
> sh mvnw -Prelease verify artifact:compare -Dreference.repo=$NEXUS_REPO
> # If preferred, augment `mvnw` with `-DskipTests` to speed things up
>
> If you have code-related objections, *DO NOT* share them by responding to
> this email, but start a new email thread instead, please.
>
> == Release notes
>
> This release contains a big revamp to the website build and several other
> minor enhancements.
>
> === Website build changes
>
> The website build system is migrated from `asciidoctor-maven-plugin` to
> Antora. This implies that `src/site` and `generate-email.sh` files need to
> be adapted, and `target/site` can be viewed without needing a local web
> server.
>
> The Maven `site` phase is re-engineered such that _generated sources_
> (i.e., `src/site/_release_notes` and `src/site/_constants.adoc`) will be
> targeted to `target/generated-site` and the website will be built from
> there. This avoids the need to commit generated sources to the repository
> and, hence, works around changelog merge conflict problems.
>
> === Website deployment changes
>
> The newly added `site-deploy-reusable.yaml` GitHub Actions workflow
> enables to automate the website deployment. Using the
> `-site--out` branch naming convention, the
> Maven `site` goal running on
>
> * the `main` branch populates the `main-site-stg-out` branch serving the `
> logging.staged.apache.org/logging-parent`
> 
> * the `main-site-pro` branch populates the `main-site-pro-out` branch
> serving the `logging.apache.org/logging-parent`
> 
> * the `release/` branch populates the
> `release/-site-stg-out` branch serving the `
> logging.staged.apache.org/logging-parent-`
>
> Refer to the usage and project release instructions pages for details.
>
> === Added
>
> * Add `coverage` profile to generate a test coverage report (#140)
> * Add `deploy-site-yaml` GitHub actions workflow to automate the website
> deployment
> * Add instructions on XML schema publication (#138)
>
> === Changed
>
> * Replace `process-sbom` script with CycloneDX plugin configuration (#105)
> * Support parallel releases by uploading the distribution to
> `/` folders. This is needed for parallel Log4j 2 and 3
> releases. (#139)
> * Migrate website support from `asciidoctor-maven-plugin` to Antora
>
> === Updated
>
> * Update `com.diffplug.spotless:spotless-maven-plugin` to version `2.43.0`
> (#108)
> * Update `com.github.spotbugs:spotbugs-maven-plugin` to version `4.8.4.0`
> (#156)
> * Update `com.google.errorprone:error_prone_core` to version `2.26.1`
> (#134)
> * Update `com.palantir.javaformat:palantir-java-format` to version
> `2.43.0` (#154)
> * Update `org.apache.logging.log4j:log4j-changelog-maven-plugin` to
> version `0.8.0` (#146)
> * Update `org.apache.maven.plugins:maven-artifact-plugin` to version
> `3.5.1` (#149)
> * Update `org.codehaus.mojo:flatten-maven-plugin` to version `1.6.0` (#102)
> * Update `org.cyclonedx:cyclonedx-maven-plugin` to version `2.8.0` (#145)
>

[ANNOUNCE] Apache Logging Parent `11.0.0` released

2024-04-18 Thread Volkan Yazıcı 
Apache Logging Parent team is pleased to announce the `11.0.0`
release. This project contains the parent POM for other Maven-based
Apache Logging Services projects. For further information (support,
download, etc.) see the project website[1].

[1] https://logging.apache.org/logging-parent

== Release notes

This release contains a big revamp to the website build and several other
minor enhancements.

=== Website build changes

The website build system is migrated from `asciidoctor-maven-plugin` to
Antora. This implies that `src/site` and `generate-email.sh` files need to
be adapted, and `target/site` can be viewed without needing a local web
server.

The Maven `site` phase is re-engineered such that _generated sources_
(i.e., `src/site/_release_notes` and `src/site/_constants.adoc`) will be
targeted to `target/generated-site` and the website will be built from
there. This avoids the need to commit generated sources to the repository
and, hence, works around changelog merge conflict problems.

=== Website deployment changes

The newly added `site-deploy-reusable.yaml` GitHub Actions workflow enables
to automate the website deployment. Using the
`-site--out` branch naming convention, the
Maven `site` goal running on

* the `main` branch populates the `main-site-stg-out` branch serving the `
logging.staged.apache.org/logging-parent`
* the `main-site-pro` branch populates the `main-site-pro-out` branch
serving the `logging.apache.org/logging-parent`
* the `release/` branch populates the
`release/-site-stg-out` branch serving the `
logging.staged.apache.org/logging-parent-`

Refer to the usage and project release instructions pages for details.

=== Added

* Add `coverage` profile to generate a test coverage report (#140)
* Add `deploy-site-yaml` GitHub actions workflow to automate the website
deployment
* Add instructions on XML schema publication (#138)

=== Changed

* Replace `process-sbom` script with CycloneDX plugin configuration (#105)
* Support parallel releases by uploading the distribution to
`/` folders. This is needed for parallel Log4j 2 and 3
releases. (#139)
* Migrate website support from `asciidoctor-maven-plugin` to Antora

=== Updated

* Update `com.diffplug.spotless:spotless-maven-plugin` to version `2.43.0`
(#108)
* Update `com.github.spotbugs:spotbugs-maven-plugin` to version `4.8.4.0`
(#156)
* Update `com.google.errorprone:error_prone_core` to version `2.26.1` (#134)
* Update `com.palantir.javaformat:palantir-java-format` to version `2.43.0`
(#154)
* Update `org.apache.logging.log4j:log4j-changelog-maven-plugin` to version
`0.8.0` (#146)
* Update `org.apache.maven.plugins:maven-artifact-plugin` to version
`3.5.1` (#149)
* Update `org.codehaus.mojo:flatten-maven-plugin` to version `1.6.0` (#102)
* Update `org.cyclonedx:cyclonedx-maven-plugin` to version `2.8.0` (#145)

Re: [Log4j] In 2.x, drop log4j-mongodb3 and add log4j-mongodb5

2024-04-18 Thread Gary D. Gregory 
TY for your help Piotr.

The PR for the 2.x part is here 
https://github.com/apache/logging-log4j2/pull/2486

Gary

On 2024/04/18 02:58:39 "Gary D. Gregory" wrote:
> Hi Piotr, 
> 
> Please see the branch feature/2.x/mongodb-next and its failing tests.
> 
> TY,
> Gary
> 
> On 2024/04/17 21:59:45 "Gary D. Gregory" wrote:
> > This is the plan that Piotr and I came up with one addition (1c):
> > 
> > 1. Branch 2.x
> > 1.a. Drop module log4j-mongodb3
> > 1.b. Add module log4j-mongodb (no number) that contains one class that 
> > instantiates the log4j-mongodb4 provider. XML element is MongoDb.
> > 1.c. Deprecate module log4j-mongodb4 in favor of log4j-mongodb
> > 
> > 2. Branch main
> > 2.a. Rename module log4j-mongodb4 to module log4j-mongodb 
> > 2.b. Rename XML element MongoDb4 to MongoDb
> > 
> > Gary
> > 
> > On 2024/04/17 19:49:40 "Piotr P. Karwasz" wrote:
> > > Hi Gary,
> > > 
> > > On Wed, 17 Apr 2024 at 21:23, Gary Gregory  wrote:
> > > > But then your config has to say  AND depend on the mongodb5
> > > > module! Still confusing 😕
> > > 
> > > There is actually a rarely used feature of our plugin system, where a
> > > plugin named `Foo` can actually create an object of type `Bar`. See
> > > for example the `LoggerConfig.Root` plugin that actually creates an
> > > object of type `LoggerConfig`.
> > > 
> > > In your config you will use `MongoDb5`, but the provider will be of
> > > type MongoDb4Provider.
> > > 
> > > Piotr
> > > 
> > 
>