-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PoolingClientConnectionManager class def not found #24
Comments
New data point: I created a new empty lein app project and added [amazonica "0.1.22"] as the only project dependency. I then nuked my .m2 directory and ran Here are the org.apache libs pulled in by my app:
and here are the further libs pulled in by the empty project:
Still not sure I understand why it's happening, but I can at least show that it's likely related to a version conflict somewhere in the load path. It looks like httpcore added support for the connection pooling in 4.2, so if my app is pulling in 4.1 and amazonica is seeing that instead of the 4.2 version, that might explain the NoClassDefFoundError. |
I just discovered the joys of Live and learn, I suppose. Sorry for the spam. |
I'm cleaning up a lein project's deps, and after shuffling around some namespaces and updating the amazonica project.clj dependency to use 0.1.22, I'm getting a new error when calling s3/get-object:
I tried resetting my amazonica dependency back to the previous version 0.1.15, but I'm still getting the error. It looks like the aws-sdk jar updated the ConnectionManagerFactory code when it bumped to version 1.5.0, which amazonica was including a bit before version 0.1.15 if I'm not mistaken.
Any idea why this is happening now? As part of my project refactoring, I removed some dependencies from the project. Is there any reason why amazonica would be dependent on any other libraries being present in the project?
The text was updated successfully, but these errors were encountered: