Re: [log4j] The great plugin migration - can we donate some plugins to more appropriate maintainers?

2022-06-07 Thread Matt Sicker
I think the appender API has been stable since 2.0. I do have a backlog item about adding an async API for appenders, but that would be additive. — Matt Sicker > On Jun 7, 2022, at 19:03, Robert Middleton wrote: > > It seems to me that this would only work if a) there exists a stable > API/AB

Re: [log4j] The great plugin migration - can we donate some plugins to more appropriate maintainers?

2022-06-07 Thread Robert Middleton
It seems to me that this would only work if a) there exists a stable API/ABI for log4j and b) sufficient demand for the appenders exists. If a stable API/ABI doesn't exist, then the new maintainers would be on the hook for any changes that log4j made, which seems unreasonable to me. -Robert Middle

Re: LogManager.getContext(true)

2022-06-07 Thread Piotr P. Karwasz
Hi all, On Tue, 7 Jun 2022 at 20:22, Matt Sicker wrote: > For the record, I like Piotr's idea on repurposing this parameter to > allow for better caching of LoggerContext in the anchor spot. This > should help with some test parallelization efforts we're working on. I believe this can help in mo

Re: LogManager.getContext(true)

2022-06-07 Thread Ralph Goers
I would think we would want to use some sort of JunitContextSelector and modify PropertiesUtil so that JUnit can provide the SystemProperties. You do not want to point the external context to JUnit’s ExtensionContext. Instead, you should add it as a key to the externalMap. Ralph > On Jun 7, 2

Re: LogManager.getContext(true)

2022-06-07 Thread Piotr P. Karwasz
Hi Volcan, On Tue, 7 Jun 2022 at 21:04, Volkan Yazıcı wrote: > Piotr, thanks so much for sparing time for test parallelization. Is there > anything else we can do rather than thread-local `LoggerContext`s? Can't we > configure a `ContextSelector` for tests such that it will attach the > `LoggerCo

Re: LogManager.getContext(true)

2022-06-07 Thread Volkan Yazıcı
I have the impression that the purpose of `currentContext` is already ambiguous and it is not clearly implemented, if not already bloated. I am not sure repurposing this would be a good idea. This said, I am far from being an expert in that area. Piotr, thanks so much for sparing time for test par

Re: [log4j] The great plugin migration - can we donate some plugins to more appropriate maintainers?

2022-06-07 Thread Piotr P. Karwasz
Hi, On Tue, 7 Jun 2022 at 20:17, Matt Sicker wrote: > * JDBC/JPA appenders -> ? (Eclipse Jakarta perhaps?) I would try EclipseLink, since Hibernate made their choice a long time ago. > * JMS appender (could go to ActiveMQ or Jakarta) An in-house collaboration with ActiveMQ seems more realistic

Re: LogManager.getContext(true)

2022-06-07 Thread Matt Sicker
For the record, I like Piotr's idea on repurposing this parameter to allow for better caching of LoggerContext in the anchor spot. This should help with some test parallelization efforts we're working on. On Mon, Jun 6, 2022 at 1:36 AM Piotr P. Karwasz wrote: > > Hi all, > > While working on test

[log4j] The great plugin migration - can we donate some plugins to more appropriate maintainers?

2022-06-07 Thread Matt Sicker
Hey all, I was wondering if you'd all be on board for 3.x to try and move some of our 3rd party integration plugins to their respective projects rather than maintaining them here. For example, all the networked appender plugins and other plugins that typically require a third party client library