Ralph, count me in for such a change. I really want to have separate sub-projects for such modules. This will extremely speed up build/release times too, which is nowadays of uttermost importance to my peace of mind while developing.
This said, I am reluctant about such a major change when we are this close to the 3.0.0 release. I guess this would definitely postpone the 3.0.0 release to 2022. This will probably break the backward compatibility at least for the artifact groupId, am I wrong? Not to mention that the entire website needs to be adapted to this multi-project setup too. Is there anything else? On Thu, Jun 3, 2021 at 5:31 PM Ralph Goers <ralph.go...@dslextreme.com> wrote: > Yeah - I have proposed moving all these extra integrations to a separate > repo but > I’ve never gotten consensus. I’d prefer to have a project like > log4j-pubsub where > things like JMS, JeroMQ, etc can go live, log4j-nosql for all the nosql > modules, etc. > The problem seems to be that some people believe that we would have to cut > a > release of those every time we do a log4j release. > > If we were to do that 3.0 would be the right time. >
