Replies: 1 comment
|
This is the Testcontainers 2.0 module-coordinate change rather than missing entries in the BOM. I checked the published 2.0.2 BOM. It manages both of the new artifact IDs: The Gradle configuration should therefore use the prefixed artifact names while allowing the BOM to provide their versions: dependencies {
testImplementation(
platform("org.testcontainers:testcontainers-bom:2.0.2")
)
testImplementation(
"org.testcontainers:testcontainers-postgresql"
)
testImplementation(
"org.testcontainers:testcontainers-junit-jupiter"
)
}Coordinates such as The published BOM can be inspected directly here: testcontainers-bom-2.0.2.pom. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I tried upgrading from earlier versions to 2.0.2 to address the bug described in #11212
While troubleshooting, I followed the manual and attempted to import the BOM in my build.gradle, but gradle could not resolve the postgresql or junit-jupiter artifacts under the groupId org.testcontainers.
After investigating Maven Central, I found two postgresql artifacts. The one without the prefix does not include version 2.0.2, while testcontainers-postgresql does. That led me to realize that many submodules were renamed with a prefix starting in 2.0.0, which was not immediately obvious from the BOM.
It appears the BOM’s build.gradle may be missing the prefixed artifact names for several submodules.
All reactions