Force consistent AWS SDK version across the build - #1485
Merged
Conversation
Spring AI's bedrock/bedrock-converse starters (added for BedrockProvider) transitively pull a newer AWS SDK release than awsSdkVersion, which embedded, cloudServices, and professional's own direct AWS SDK dependency already use. AWS SDK v2 requires every software.amazon.awssdk artifact to share one version, so the skew left two copies of classes like software.amazon.awssdk.regions.Region loaded across the embedded/module classloader boundary, surfacing at server startup as a LinkageError (loader constraint violation) rather than a build-time conflict -- this is what's been failing TeamCity's upgrade validation and other suites since the Bedrock dependency landed.
labkey-adam
approved these changes
Aug 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale
Spring AI's bedrock/bedrock-converse starters (added for BedrockProvider) transitively pull a newer software.amazon.awssdk release than awsSdkVersion, which embedded, cloudServices, and professional's own direct AWS SDK dependency already use. AWS SDK v2 requires every software.amazon.awssdk artifact to share one version, so the skew left two different copies of classes like software.amazon.awssdk.regions.Region loaded across the embedded (Spring Boot boot classpath) / module classloader boundary. At server startup this surfaces as java.lang.LinkageError: loader constraint violation rather than a build-time dependency conflict, and since TeamCity servers run with -DterminateOnStartupFailure=true the JVM exits immediately -- this has been failing TeamCity's upgrade validation suite (and others) since the Bedrock dependency landed on 2026-08-21.
Related Pull Requests
Changes
eachDependencyrule to the rootresolutionStrategyblock that forces everysoftware.amazon.awssdk:*artifact toawsSdkVersion, regardless of which module or transitive dependency pulls it in. Verified via:server:modules:premiumModules:professional:dependenciesthat the AWS SDK tree now resolves uniformly toawsSdkVersioninstead of split 2.29.50/2.41.22.