Re: The roadmap to Log4j 3.0.0

2022-04-01 Thread Matt Sicker
Given the modularity of 3.x, as long as we provide both the jakarta and javax versions of each, I think we'll be ok. We can revisit removal of javax variants in the future if they become a burden on maintenance (e.g., incompatible with newer versions of Java). On Fri, Apr 1, 2022 at 12:08 PM Ralph

Re: The roadmap to Log4j 3.0.0

2022-04-01 Thread Ralph Goers
While we need to support jakarta I am not sure it is time to drop javax. Our history is to support things until the active user base is very low. Last I heard javax usage was still larger than jakarta. Ralph > On Apr 1, 2022, at 9:24 AM, Matt Sicker wrote: > > On the javax->jakarta idea, I

Re: The roadmap to Log4j 3.0.0

2022-04-01 Thread Matt Sicker
On the javax->jakarta idea, I think that's a good idea. Every plugin we have that uses a javax API should have a jakarta equivalent created and promoted over the old version. We have several of them already; I'm not sure which ones remain. On Fri, Apr 1, 2022 at 6:22 AM Gary Gregory wrote: > > Ye

Re: The roadmap to Log4j 3.0.0

2022-04-01 Thread Gary Gregory
Yes, thank you Piotr, it's tremendously helpful :-) Gary On Fri, Apr 1, 2022, 03:28 Ralph Goers wrote: > Thank you for that! > > Ralph > > > On Mar 31, 2022, at 12:53 PM, Piotr P. Karwasz > wrote: > > > > Hello, > > > > On Mon, 28 Mar 2022 at 22:02, Piotr P. Karwasz > wrote: > >> The `log4j-1

Re: The roadmap to Log4j 3.0.0

2022-04-01 Thread Jochen Wiedmann
On Tue, Mar 29, 2022 at 9:11 PM Matt Sicker wrote: > > I don’t know if any new javax APIs are defined anymore. There’s JakartaEE for > the new APIs, though that’s through Eclipse at this point I think. > > Also, for a generic plugin library, there are some things I’d likely do > slightly differe

Re: The roadmap to Log4j 3.0.0

2022-04-01 Thread Ralph Goers
Thank you for that! Ralph > On Mar 31, 2022, at 12:53 PM, Piotr P. Karwasz > wrote: > > Hello, > > On Mon, 28 Mar 2022 at 22:02, Piotr P. Karwasz > wrote: >> The `log4j-1.2-api` code seems synchronized between `master` and >> `release-2.x` up to January 20th. Since part of the desynchroniza

Re: The roadmap to Log4j 3.0.0

2022-03-31 Thread Piotr P. Karwasz
Hello, On Mon, 28 Mar 2022 at 22:02, Piotr P. Karwasz wrote: > The `log4j-1.2-api` code seems synchronized between `master` and > `release-2.x` up to January 20th. Since part of the desynchronization > that occurred afterwards is my fault and some of my changes are built > on top of Gary's, I can

Re: The roadmap to Log4j 3.0.0

2022-03-29 Thread Matt Sicker
I don’t know if any new javax APIs are defined anymore. There’s JakartaEE for the new APIs, though that’s through Eclipse at this point I think. Also, for a generic plugin library, there are some things I’d likely do slightly differently than in here since backward compatibility wouldn’t be rel

Re: The roadmap to Log4j 3.0.0

2022-03-29 Thread Gary Gregory
It's just a question, not a request. Gary On Tue, Mar 29, 2022, 03:31 Ralph Goers wrote: > Gary, > > The work for this was covered in LOG4J2-2621 which was resolved in > June 2019 and discussed on the dev list a few times. It is a little late > to > be asking that question. > > Ralph > > > On M

Re: The roadmap to Log4j 3.0.0

2022-03-29 Thread Ralph Goers
Gary, The work for this was covered in LOG4J2-2621 which was resolved in June 2019 and discussed on the dev list a few times. It is a little late to be asking that question. Ralph > On Mar 28, 2022, at 12:20 PM, Gary Gregory wrote: > > Hi Matt, > > Why isn't the code in log4-plugins in log4

Re: The roadmap to Log4j 3.0.0

2022-03-29 Thread Ralph Goers
Yes, I would really like to see the plugin system moved to something like Commons Plugins. Of course, it would be even better as javax.plugins! Of course, moving it does mean users will now be required to include log4j-plugins in addition to log4j-api and log4j-core. However, I don’t necessaril

Re: The roadmap to Log4j 3.0.0

2022-03-28 Thread Piotr P. Karwasz
Hello, On Sun, 27 Mar 2022 at 23:59, Matt Sicker wrote: > * There are dozens (possibly hundreds) of commits that have only been applied > to release-2.x which need to be copied to master. The `log4j-1.2-api` code seems synchronized between `master` and `release-2.x` up to January 20th. Since pa

Re: The roadmap to Log4j 3.0.0

2022-03-28 Thread Matt Sicker
Originally, it was because most of that code had to be there where the annotations were. Now some of that code can be moved back to core, though some of it would still need to remain for the annotation processing stuff. Ralph had suggested recently that the plugin code could form a useful basis

Re: The roadmap to Log4j 3.0.0

2022-03-28 Thread Gary Gregory
Hi Matt, Why isn't the code in log4-plugins in log4j-core? Gary On Sun, Mar 27, 2022, 16:59 Matt Sicker wrote: > Hey all, after making a lot of serious progress toward what I’ve been > alternatively referring to as the “Mean Bean Machine” or the “Great > Inversion”, I’m finally coming to a log

The roadmap to Log4j 3.0.0

2022-03-27 Thread Matt Sicker
Hey all, after making a lot of serious progress toward what I’ve been alternatively referring to as the “Mean Bean Machine” or the “Great Inversion”, I’m finally coming to a logical conclusion of this (only have a couple remaining plugin types to refactor). While it took a few tries using differ