Systematic approach with Maven to deal with dependency hell
问题 I'm struggling with how to approach jar dependency hell. I have a Maven-IntelliJ Scala project that uses some aws sdk's. Recently adding the kinesis sdk has introduced incompatible versions of Jackson. My question is : how do I systemically approach the problem of Jar hell? I understand class loaders and how maven chooses between duplicate Jars, but I am still at a loss regarding actual practical steps to fix the issue. My attempts at the moment are based on trial and error, and I am