You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
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.
Beta Was this translation helpful? Give feedback.
All reactions