On publishing test JARs

I don't know what was our earlier policy on test JARs (if we have any at all), but I suggest we stop deploying to Nexus anything that is not meant for public consumption: api, core, adapters, filters, etc. Now are we supposed to spend hours fixing the tests of an individual because he happened to d

Log4j team vs Logging Services team

I propose redirecting all "Team" links in Log4j, log4cxx, etc. to the Logging Services Team page . I know Ralph disagrees with me[, hence this email]. He wants the Log4j project to have its own "Team" page where its content is populated from `pom.xml`. I

Broken Javadoc URL

While fixing the javadoc for the 2.20.0 release, I renamed the path from `//apidocs` to `/javadoc/`. As the user issue below explains, this got some people angry. I have already temporarily fixed the issue by creating directory symlinks. For a permanent solution, I see two options: 1. Configure

Re: On publishing test JARs

Please keep publishing test jars, at least the core and api jars. One of these contains Junit rules and utilities that are very useful and I reply on those for many projects. Gary On Wed, Feb 22, 2023, 03:04 Volkan Yazıcı wrote: > I don't know what was our earlier policy on test JARs (if we hav

Re: On publishing test JARs

I should add that I don't expect any kind of BC compatibility, I take them as they are and adapt. Gary On Wed, Feb 22, 2023, 07:23 Gary Gregory wrote: > Please keep publishing test jars, at least the core and api jars. One of > these contains Junit rules and utilities that are very useful and I

Re: On publishing test JARs

I understand the use case, but I don't agree on the solution. You are using Log4j tests. Do I really need to explain why this is a bad idea? Imagine you in a similar way used Kernel tests and posed this question in the mailing lists and Linus writing you a response... What I would find approachabl

Re: On publishing test JARs

Both Piotr and I have responded to that Jira issue and I marked it as resolved. We do publish test jars. They just no longer use a classifier. Volkan, the test jars we publish are expected to be used for public consumption. Note that I did NOT include Json Template Layout’s test jar in the dis

Re: Log4j team vs Logging Services team

Yes, I disagree for a few reasons: 1. Not all the people listed in the logging services team page contribute to each project. While it is probably OK for Log4j because most Logging Services members are contributing to Log4j the same would not be true for Log4cxx and Log4Net. 2. We are not goin

Re: Broken Javadoc URL

Answering right now my preference is number 1 however that could change if no other complaints are made regarding the web site. We eliminated a number of project reports that users might yet complain about. So adding in the module directories makes it much easier to restore missing reports shoul

Re: On publishing test JARs

Right, there are intentionally public test fixtures in API test and Core test (and eventually plugin test). While they don’t guarantee strict backward compatibility, they are intended for use outside of this project. > On Feb 22, 2023, at 10:02 AM, Ralph Goers wrote: > > Both Piotr and I have