Re: [LOGGING] 2.0

2024-02-10 Thread Piotr P. Karwasz
Hi Gary, On Sat, 10 Feb 2024 at 17:26, Gary Gregory wrote: > My main driver for the next version is to drop support and dependency > on the Log4j 1.x JARs file(s). I speak of JAR files here as opposed to > APIs, see below. Log4JLogger is disabled by default in version 1.3.0 (cf. [1]) and the dep

Re: [LOGGING] 2.0

2024-02-10 Thread Elliotte Rusty Harold
I'm fine with #1 or #2 if you can make either work. I actively dislike #3. In particular I do not think we should change package names or Maven coordinates. I think it is OK and in this case highly advisable to break API compatibility solely by removing support for obsolete and mostly unused funct

Re: [LOGGING] 2.0

2024-02-10 Thread Gary Gregory
Experiment for (1): https://github.com/garydgregory/commons-logging/tree/log4j1-log42-api Yes, I know there are test failures (they make sense, and that needs adjusting). Gary On Sat, Feb 10, 2024 at 11:26 AM Gary Gregory wrote: > > Hi All: > > I want to focus on content before we decide what l

Re: [LOGGING] 2.0

2024-02-10 Thread Gary Gregory
Below. On Sat, Feb 10, 2024 at 12:11 PM sebb wrote: > > On Sat, 10 Feb 2024 at 16:27, Gary Gregory wrote: > > > > Hi All: > > > > I want to focus on content before we decide what label to put on the > > next release. Then, we can see if we want to break binary > > compatibility (BC) for a Common

Re: [LOGGING] 2.0

2024-02-10 Thread sebb
On Sat, 10 Feb 2024 at 16:27, Gary Gregory wrote: > > Hi All: > > I want to focus on content before we decide what label to put on the > next release. Then, we can see if we want to break binary > compatibility (BC) for a Commons Logging 2.0.0. > > My main driver for the next version is to drop su

Re: [LOGGING] 2.0

2024-02-10 Thread Gary Gregory
Hi All: I want to focus on content before we decide what label to put on the next release. Then, we can see if we want to break binary compatibility (BC) for a Commons Logging 2.0.0. My main driver for the next version is to drop support and dependency on the Log4j 1.x JARs file(s). I speak of JA

[LOGGING] 2.0

2024-02-10 Thread Elliotte Rusty Harold
I'd like to plan and start working on a 2.0 release of commons-logging with the specific goal of resolving the large number of out of date, unsupported, old libraries that this project pulls into so many dependency trees. There's been some discussion of a 2.0 release in JIra at https://issues.apac