Hi, I’m currently working on resolving some of the dependency version issues we are having. Mostly people will not have noticed, but currently we’re pulling in up to 4 different versions of a jar in our build. This can cause many extremely hard to spot problems.
While trying to fix a problem with metrics-core in version 4.2.7 but pulling in on older version in Ratis I noticed us using: <ratis.version>2.5.2-a4398bf-SNAPSHOT</ratis.version> This is extremely problematic. Currently the Apache Nexus server only keeps 5 SNAPSHOT versions and then deletes old ones. This means that we regularly have to bump the SNAPSHOT version of Ratis. This got me thinking and I checked the release branch for the 1.2.x branch. Here we’re using the same. The problem with using SNAPSHOTS on master is not that severe, but using them in releases it very problematic. I guess we’ll only be able to build our last release for a few more days/weeks and then it will no longer be buildable. Are we relying on things in Ratis, that are not yet released? We should probably encourage the Ratis folks to head for a new release (Ideally with my latest Ratis-PR merged). Chris
