TY for your help Piotr. The PR for the 2.x part is here https://github.com/apache/logging-log4j2/pull/2486
Gary On 2024/04/18 02:58:39 "Gary D. Gregory" wrote: > Hi Piotr, > > Please see the branch feature/2.x/mongodb-next and its failing tests. > > TY, > Gary > > On 2024/04/17 21:59:45 "Gary D. Gregory" wrote: > > This is the plan that Piotr and I came up with one addition (1c): > > > > 1. Branch 2.x > > 1.a. Drop module log4j-mongodb3 > > 1.b. Add module log4j-mongodb (no number) that contains one class that > > instantiates the log4j-mongodb4 provider. XML element is MongoDb. > > 1.c. Deprecate module log4j-mongodb4 in favor of log4j-mongodb > > > > 2. Branch main > > 2.a. Rename module log4j-mongodb4 to module log4j-mongodb > > 2.b. Rename XML element MongoDb4 to MongoDb > > > > Gary > > > > On 2024/04/17 19:49:40 "Piotr P. Karwasz" wrote: > > > Hi Gary, > > > > > > On Wed, 17 Apr 2024 at 21:23, Gary Gregory <garydgreg...@gmail.com> wrote: > > > > But then your config has to say <MongoDb4> AND depend on the mongodb5 > > > > module! Still confusing 😕 > > > > > > There is actually a rarely used feature of our plugin system, where a > > > plugin named `Foo` can actually create an object of type `Bar`. See > > > for example the `LoggerConfig.Root` plugin that actually creates an > > > object of type `LoggerConfig`. > > > > > > In your config you will use `MongoDb5`, but the provider will be of > > > type MongoDb4Provider. > > > > > > Piotr > > > > > >
