@M451 Could you explain 'better compatibility' please?

@marcuslinke

I'm using this lib for a os project that integrates into another project which is using jackson 2.1.2. Since 2.1.2 is loaded in the parent classloader, docker-java's 2.3.3 dependency is never loaded and 2.1.2 is used. This results in an "method not found" exception for some operations such as pull and start when getFactory of jackson's fasterxml is called.

Since there is no hard requirement for 2.3.3 within the docker-java project itself, I'd suggest to use lower dependency versions if possible to maximize compability in such dependency conflict szenarios (also known as jar hell) - most libs are compatible with their predecessor versions but not vice-versa.

I know this is a very special case but I reluctantly would like to fork just in order to get this lib running.

Maybe this is related: https://issues.jenkins-ci.org/browse/JENKINS-25692

@albers

I guess it's the same issue but with another dependency. That's why I'd like to suggest to use dependency versions as high as required but as low as possible.

@M451 Thanks for the explanation. I will try to integrate this in the next few days.

@marcuslinke
can you tell me the status on this? Do you think you could merge atleast this dep. into the project so it's included within the latest snapshot?

@M451 Merged. Thanks! I will publish a new release probably next weekend.