|Re: [jgit-dev] Introduction of new dependency (Apache Commons Codec or Guava) into JGit?|
On Fri, Apr 7, 2023 at 12:16 PM Xeno Amess <xenoamess@xxxxxxxxx> wrote: > > Hi. > I have some commits in both repos so I could say they be both good repos, with good maintenance from good people. > However according to the situation here I think commons compress is more suitable. > As: > 1. It evolves slower. Well commons libs actually don't change much things in these 10 years or so, especially when you see it from compatibility side. > However guava, well, they moves really fast, and have more than 50+ major versions. So as a basic lib jgit might better choose commons compress.(well if you saying for a micro-service things might be quite different.) > And guava have some versions, for jre, for android, etc. > So I would not recommend you using guava as a lib, please imagine if a microservice using a different guava version than you choose and wanna use jgit also, well the BC issues would be a headache(even nightmare) > 2. It is smaller than guava. guava's jar seems 10+ times larger than commons-compress. A note that I'm looking into codec, not compress (which is already used by JGit). But I think that most of your points also apply to codec. Let me try out codec and see how it goes.
Back to the top