Closed clintoncampbell closed 6 years ago
There were no changes specific to Jackson or OSGi in that version. I am not sure whats going on. Can you try latest version (1.11.243) and see if you can reproduce the issue?
Have you been able to reproduce the issue with the latest version of the SDK?
Haven't had a chance to try yet, but I think I can make it happen today. Sorry about that.
On Mon, Dec 11, 2017 at 12:00 PM, Andrew Shore notifications@github.com wrote:
Have you been able to reproduce the issue with the latest version of the SDK?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/aws/aws-sdk-java/issues/1407#issuecomment-350840324, or mute the thread https://github.com/notifications/unsubscribe-auth/AHDM7PNW5nljJMwBCkYIXg0sG9EnrGR4ks5s_YnSgaJpZM4QzBYR .
Apologies for the delay. Yes, we are still encountering the errors on the latest version.
Seems to be a dependency conflict with another part of the framework. Issue resolved using the new bundled version of the jar.
Yesterday, we began to experience a build failure in our development environment that was quickly linked to the 1.11.240 version of the SDK. After a fair amount of diagnosis, I believe that the issue is related to dependency bundling and OSGi.
The issue is presenting itself in a Lucee 5.2 based application running on top of Tomcat 8.0.47. Building the same container with aws-java-sdk-1.11.233.jar works well, though we begin to see ClientConfiguration instantiation issues linked with Jackson as soon as we update the jar to 1.11.240. Lucee Server provides a decent picture of what is happening in terms of OSGi, and in both cases I can see that the proper dependencies are being loaded.
The following image depicts a portion of the stack trace indicating an issue with loading the correct classes from jackson.
Note that I ran both scenarios (1.11.233 and 1.11.240) with the jars packaged with the 1.11.240 sdk, so I do not believe the issue is with the dependencies themselves, but how 1.11.240 consumes them.