Description of changes:
Creates the X-Ray Agent JAR as an Uber JAR containing:
X-Ray Agent Plugin
X-Ray SDK Core module
AWS SDK V1 (and its transitive dependencies)
X-Ray SDK SQL module
X-Ray SDK AWS SDK handler module
X-Ray SDK AWS SDK V2 handler module
This allowed us to remove the awkward separate AWS SDK handler libraries that customers would also have to depend on to have AWS SDK requests traced. I removed AWS SDK V2 Handler dependency on the AWS SDK V2 itself, so we wouldn't have to bundle both versions of AWS SDK into the jar. Also simplified the publishing logic a little bit, added some more safety to AWS SDK handlers, and removed the old reflective way of getting the AWS SDK handlers.
Tested on a Spring boot sample app with varied dependency versions (including 4-year-old versions of AWS SDK and Jackson). Was able to accomplish both auto and manual instrumentation with a Recorder shared between the agent and application.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issue #, if available: fixes #7
Description of changes: Creates the X-Ray Agent JAR as an Uber JAR containing:
This allowed us to remove the awkward separate AWS SDK handler libraries that customers would also have to depend on to have AWS SDK requests traced. I removed AWS SDK V2 Handler dependency on the AWS SDK V2 itself, so we wouldn't have to bundle both versions of AWS SDK into the jar. Also simplified the publishing logic a little bit, added some more safety to AWS SDK handlers, and removed the old reflective way of getting the AWS SDK handlers.
Tested on a Spring boot sample app with varied dependency versions (including 4-year-old versions of AWS SDK and Jackson). Was able to accomplish both auto and manual instrumentation with a Recorder shared between the agent and application.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.