-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@Testcontainers is not found in parentclass #1843
Comments
@abendt-mhp could you please try 1.12.0? I think it may be caused by #1530 |
sure. its the same exception with v 1.12.0. the workaround also works |
@abendt-mhp thanks! FYI this task is up for grabs if anyone wants to contribute it :) We will eventually take a look, but would also appreciate a fix contributed. I confirm that |
I'd be interested taking this on |
@bmuskalla thanks! It is yours 👍 I will soft timebox it to 7 days, just so that we can check in one week whether you are still working on it :) |
…#1843) * Updated existing test with now expected behaviour * @testcontainers is now @inherited
@bsideup friendly ping :) |
@bmuskalla thanks for the ping! 👍 there is one trivial thing (codestyle), happy to merge after 🎉 |
Hello! Could you tell when this PR will be merged approximately? |
am waiting for a new release that includes the fix as well :) |
@Nipel-Crumple there is a PR (#1845) from @bmuskalla that waits a bit of polishing before we merge it |
is it just because of the star import? i could fix that in case |
…#1843) * Updated existing test with now expected behaviour * @testcontainers is now @inherited
Sorry, I totally missed the notification on this one. Pushed a new PR (#2001) for this with the imports fixed (and mssed up the old PR) |
@bmuskalla thank you! 👍 |
* Updated existing test with now expected behaviour * @testcontainers is now @inherited
Fixed by #2001 |
i am currently trying to upgrade from testcontainers version 1.11.4 to 1.12.1
it looks there might be an regression between that versions.
our current code (using v 1.11.4 looks like that). It uses an abstract base class that contains the @testcontainers annotation.
this setup causes an runtime exception when upgrading to v 1.12.1:
i can work around that by putting the @testcontainers annotation directly into the concrete test class:
The text was updated successfully, but these errors were encountered: