Maybe if want to only use the latest driver for main, we should rename the module and classes and drop the "4". That or go with what I initially suggested.
Gary On Wed, Apr 17, 2024, 12:18 PM Gary Gregory <garydgreg...@gmail.com> wrote: > Hi Piotr, > > Having mongodb4 module depend on the mongodb 5 driver sure is confusing > though. What I don't know and don't want to deal with is "I updated to the > latest log4j-mongdb5 version and my app no longer works" because it might > turn out that the newer 5.x driver drops support for older Mongo versions. > Since we established support for major versions of the driver for 3 and 4, > I thought it conceptually simpler to do the same for 5. > > WDYT? > > Gary > > On Wed, Apr 17, 2024, 11:24 AM Piotr P. Karwasz <piotr.karw...@gmail.com> > wrote: > >> Hi Gary, >> >> On Wed, 17 Apr 2024 at 16:36, Gary D. Gregory <ggreg...@apache.org> >> wrote: >> > >> > Hello All, >> > >> > In In 2.x, I would like to: >> > >> > - drop log4j-mongodb3 and >> > - add log4j-mongodb5 >> > - then do the same in 3.x >> > >> > Any objections? >> >> It is fine with me. >> >> Regarding log4j-mongodb5: MongoDB driver has already been upgraded to >> version 5.0.0 in `main` by Dependabot and the unit tests passed. Do we >> need another artifact or we just need to test it against version 4.11 >> and 5.0 of the driver? >> >> Piotr >> >