Repository navigation
feat!: Testcontainers 2.x - #8
Merged
Merged
Conversation
Testcontainers 2 renamed every module artifact — postgresql to testcontainers-postgresql, jdbc to testcontainers-jdbc and so on — and the old coordinates are not published at 2.x at all. That is what consumers hit: their core resolves to 2.x through Spring Boot while env keeps modules at 1.21.1, and ScriptUtils from database-commons 1.21.1 calls the shaded commons-io that 2.x dropped, so the first container with an init script dies with NoClassDefFoundError before a single assertion. env-selenium used that same shaded commons-io for FileUtils.ONE_GB; it is a constant now. InitScriptTest covers the path: with modules at 1.21.1 against a 2.x core it fails with that exact NoClassDefFoundError, and it passes with 2.0.5 across the board. Breaking for anyone declaring org.testcontainers module coordinates themselves — they have to rename too. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Testcontainers 2 renamed every module artifact —
postgresqltotestcontainers-postgresql,jdbctotestcontainers-jdbcand so on — and the old coordinates are not published at 2.x at all.That is what consumers hit: their core resolves to 2.x through Spring Boot 4, while env keeps the modules at 1.21.1.
ScriptUtilsfromdatabase-commons:1.21.1then calls the shadedcommons-iothat 2.x dropped, and the first container with an init script dies before a single assertion:env-seleniumused that same shadedcommons-ioforFileUtils.ONE_GB; it is a plain constant now.InitScriptTestcovers the path: with the modules at 1.21.1 against a 2.x core it fails with exactly that error, and it passes with 2.0.5 across the board.Breaking for anyone who declares Testcontainers module coordinates themselves — they have to rename too.