Re: [VOTE] Release Apache Log4j 3.0.0-beta1

On Tue, Dec 19, 2023 at 2:05 PM Gary Gregory wrote: > Do note that building from sources, not git, is an Apache requirement. Okay, but in what universe is building from a Git tag on the sources (which is, what the release:perform goal does) different from "building from sources"? Jochen

Re: [VOTE] Release Apache Log4j 3.0.0-beta1

In these universes (projects): Over the years, many RCs in many projects have created zip and tars with missing files because assembly descriptors for the Maven assembly plugin where not updated correctly or created properly in the first place. The src zip and tar is NOT (usually) a dump of EVERYTH

[log4j] Revamping Log4j website & manual tooling

As a part of the planned Log4j website & manual revamp , my proposal is to stick to what we already have (i.e., AsciiDoc) and just automate the publication

Re: [log4j] Revamping Log4j website & manual tooling

I see only one mention of Antora, the tool you are proposing. You don't have to sell us Asciidoc; we all have our opinions about it; the majority of the document is about "why not" but little "why Antora" I would be more interested in the challenges/benefits of Antora, and how such a system cou

Log4j 2.22.1 release schedule

Hi all, In the next days I would like to prepare a Log4j 2.22.1 patch release, based on this milestone: https://github.com/apache/logging-log4j2/milestone/10 Could you review the PRs attached? I am only waiting for a PR from a user (for a "good-first-issue") and `logging-parent` 10.5.0 and I am

Re: [log4j] Revamping Log4j website & manual tooling

On Wed, Dec 20, 2023 at 5:05 PM Christian Grobmeier wrote: > I see only one mention of Antora, the tool you are proposing. I am indeed **not** proposing Antora (removed its mentions), but plain AsciiDoc, which is exactly what we have in Log4j, Log4j Kotlin, Log4j Scala, Log4j Tools, Log4j Trans

[VOTE] Release Apache Log4j Kotlin API 1.4.0

This is a vote to release the Apache Log4j Kotlin API 1.4.0. Website: https://logging.staged.apache.org/log4j/kotlin GitHub: https://github.com/apache/logging-log4j-kotlin Commit: ee2d4a8efa16bb2223252329531c94e98ed6d1e6 Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-kotlin Nex

Re: [VOTE] Release Apache Log4j Kotlin API 1.4.0

Before Piotr and others start voting -1, let me make a correction: Nexus URL is incorrect. The correct one is: https://repository.apache.org/content/repositories/orgapachelogging-1251 (Matt, there is a warning about this in the release instructions. 😉) On Wed, Dec 20, 2023 at 7:08 PM Matt Sicker

Re: [log4j] Revamping Log4j website & manual tooling

On Wed, Dec 20, 2023, at 17:50, Volkan Yazıcı wrote: > On Wed, Dec 20, 2023 at 5:05 PM Christian Grobmeier > wrote: > >> I see only one mention of Antora, the tool you are proposing. > > > I am indeed **not** proposing Antora (removed its mentions), but plain > AsciiDoc, which is exactly what we h

Re: [VOTE] Release Apache Log4j 3.0.0-beta1 (RC2)

Hi Volkan, On Tue, 19 Dec 2023 at 22:00, Volkan Yazıcı wrote: > > This is a vote to release the Apache Log4j 3.0.0-beta1 RC2. > > Website: https://logging.staged.apache.org/log4j/3.x > GitHub: https://github.com/apache/logging-log4j2 > Commit: 416cd4dcf419b59c88054d2001d34c7fec010560 > Distributi

Re: [VOTE] Release Apache Log4j 3.0.0-beta1 (RC2)

+1 from me. Everything seems ok. Ralph > On Dec 19, 2023, at 2:00 PM, Volkan Yazıcı wrote: > > This is a vote to release the Apache Log4j 3.0.0-beta1 RC2. > > Website: https://logging.staged.apache.org/log4j/3.x > GitHub: https://github.com/apache/logging-log4j2 > Commit: 416cd4dcf419b59c88054

Re: [log4cxx] Release time?

If there aren't any objections, I will plan to do a release in a week or so. I'm not aware of any issues that need to be fixed, so having a new release for a new year seems like a good idea. -Robert Middleton On Mon, Nov 20, 2023 at 9:53 AM Robert Middleton wrote: > > It's been a bit over 6 mon

Re: Log4j 2.22.1 release schedule

The plan sounds good to me. I am only not comfortable with the workaround to #2065 . In a nutshell, the way Coursier/Ivy derives the effective POM doesn't match the one Maven does. Only to make Coursier/Ivy work, we add redundant dependency decla