Hello, team! Last year there was a PR in which I made an attempt to update mongo-java-driver. There were 8 failed unit tests left but I didn't manage to fix them without a help from the core development team. https://github.com/apache/jmeter/pull/390
We can use it during upgrade. Sincerely, Ihor Пт, 4 жовт. 2019 20:30 користувач Vladimir Sitnikov < [email protected]> пише: > >It’s not about size, it’s about quality and « «uptodateness » > > This would partially be solved with > https://github.com/ben-manes/gradle-versions-plugin > That is a Gradle plugin that discovers available updates on demand. > What if we upgrade to mongo-java-driver 2.11.3 to 3.11.0? > > >But even with it, we should drop MongoDB > > Does it really hurt? > The jar is small. The UI is small. It never fails CI. > > It is not like I use Mongo every day. > I just mean that there might be chicken-and-egg problem: no Mongo sampler > -> JMeter users don't even try testing MongoDB (or storing temporary data > in MongoDB instead of files). > > >let’s make a POC of it. > > After 5.2? > > Vladimir >
