Re: Delete `logging-log4j-plugins`

Requested its deletion in INFRA-24986. On Wed, Sep 13, 2023 at 3:37 PM Volkan Yazıcı wrote: > `logging-log4j-plugins` > is a practically empty repository created 7 years ago. I want to delete it. > Objections? >

Re: Renamed `master` to `main` for `logging-log4j-kotlin`

Thanks for handling that > On Sep 13, 2023, at 6:19 AM, Volkan Yazıcı wrote: > > INFRA-24976 implements the rename of `master` to `main` for the > `logging-log4j-kotlin` repository, FYI.

Re: Archive `logging-log4j-boot`

Hi Matt, On Thu, 14 Sept 2023 at 18:58, Matt Sicker wrote: > > The point of Log4j Boot was to aid in using the correct dependencies for > various optional features. As we’ve split those optional features out from > core into appropriate modules, that makes Log4j Boot moot as the individual >

Renamed `master` to `main` for `logging-log4j-scala`

INFRA-24980 implements the rename of `master` to `main` for the `logging-log4j-scala` repository, FYI.

Re: Archiving `logging-log4j-server` and `-audit`

Gary, you haven't replied to this question of mine yet. I'd like to know more about your use case. I had a call with Ralph and he stated `log4j-server` is not usable without customizations. Hence, he added, it is better suited to `log4j-samples`. I liked this idea. Do you have any objections if

Re: Switch from `maven-bundle-plugin` to `bnd-maven-plugin`

I’m in favor of using bnd-maven-plugin (as the person who introduced it in log4j-api-kotlin) mainly due to the fact that it’s a more first-class OSGi project that’s still recommended for modern OSGi development. > On Sep 13, 2023, at 4:12 AM, Piotr P. Karwasz wrote: > > Hi, > > As you

[log4j-kotlin] Preparing 1.3.0

I'd like to release `log4j-kotlin` 1.3.0, though one thing still needs to be decided: Kotlin baseline. I'd like to raise this from `1.3.72` to `1.6.21`. Thoughts? Objections?

Re: Archive `logging-log4j-boot`

Created INFRA-24989 requesting archival of `logging-log4j-boot`. On Wed, Sep 13, 2023 at 3:34 PM Volkan Yazıcı wrote: > > `logging-log4j-boot`, last touched 6 years ago, is a spin-off from > LOG4J2-1775, where it is stated that "The Log4j Boot concept can be > superseded by the increased

[VOTE] Release Apache Log4j JMX GUI 2.21.0

This is a vote to release the Apache Log4j JMX GUI 2.21.0. Source repository: https://github.com/apache/logging-log4j-jmx-gui Commit: 35d3021e995393a0f62198c2c65af8b47e42688b Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-jmx-gui Nexus:

Re: Framework for integration tests

No, some internal thing. > On Sep 14, 2023, at 3:50 PM, Gary Gregory wrote: > > Podman? > > On Thu, Sep 14, 2023, 4:42 PM Matt Sicker wrote: > >> I’ve switched from Docker and Docker Desktop to something new (not >> Rancher), but it does expose Docker compatibility APIs, so not a problem >>

Re: Framework for integration tests

Podman? On Thu, Sep 14, 2023, 4:42 PM Matt Sicker wrote: > I’ve switched from Docker and Docker Desktop to something new (not > Rancher), but it does expose Docker compatibility APIs, so not a problem > here. > > > On Sep 13, 2023, at 4:40 PM, Ralph Goers > wrote: > > > > Are you really

Re: [log4j-kotlin] Preparing 1.3.0

On Thu, Sep 14, 2023 at 2:39 PM Volkan Yazıcı wrote: > I'd like to release `log4j-kotlin` 1.3.0, though one thing still needs > to be decided: Kotlin baseline. I'd like to raise this from `1.3.72` > to `1.6.21`. Thoughts? Objections? > I don't have any objections as the current version is 1.9.x

Re: Framework for integration tests

I’ve switched from Docker and Docker Desktop to something new (not Rancher), but it does expose Docker compatibility APIs, so not a problem here. > On Sep 13, 2023, at 4:40 PM, Ralph Goers wrote: > > Are you really switching from Docker or just Docker Desktop? We moved to use > Rancher due

Re: [log4j-kotlin] Preparing 1.3.0

I’d have to make sure that I can upgrade Spinnaker to Kotlin 1.6.x, but would otherwise be ok with that at this point. > On Sep 14, 2023, at 1:38 PM, Volkan Yazıcı wrote: > > I'd like to release `log4j-kotlin` 1.3.0, though one thing still needs > to be decided: Kotlin baseline. I'd like to

Re: [VOTE] Release Apache Log4j JMX GUI 2.21.0

+1 Remko > On Sep 14, 2023, at 16:34, Volkan Yazıcı wrote: > > This is a vote to release the Apache Log4j JMX GUI 2.21.0. > > Source repository: https://github.com/apache/logging-log4j-jmx-gui > Commit: 35d3021e995393a0f62198c2c65af8b47e42688b > Distribution:

Re: Archive `logging-log4j-boot`

The point of Log4j Boot was to aid in using the correct dependencies for various optional features. As we’ve split those optional features out from core into appropriate modules, that makes Log4j Boot moot as the individual modules will do what this repo was designed to do for 2.x. I’d be

Re: Archiving `logging-log4j-server` and `-audit`

And I know there’s a Jenkins plugin based on log4j-audit. We’ve had a couple releases so far at least. > On Sep 13, 2023, at 5:01 PM, Gary Gregory wrote: > > More than once: https://logging.apache.org/log4j-audit/latest/download.html > > Gary > > On Wed, Sep 13, 2023 at 5:56 PM Ralph Goers

Re: Silly logging- prefix for artifact names

Yeah, the logging- prefix is how ASF handles multiple sub-orgs in the ASF org. > On Sep 13, 2023, at 8:05 AM, Gary Gregory wrote: > > Can we please drop the silly "logging-" prefix for all our artifacts? > > "logging-log4j-foo"? I always recoil... > > Gary

Re: Migrating `log4j-scala` to Maven

If those alternative libraries are sufficient facades, then we could consider archiving this. Otherwise, we’ll look into modernizing the build for making more regular releases again. > On Sep 13, 2023, at 11:04 AM, PJ Fanning wrote: > > My view is that in the absence of regular releases and