[Bug]: testcontainers-kafka 2.x still has split package issue

[big-andy-coates]

Module

Kafka

Testcontainers version

2.0.4

Using the latest Testcontainers version?

Yes

Host OS

MacOS

Host Arch

ARM

Docker version

Not related to Docker

What happened?

Release of version 2.x saw each module's types move into a module specific package. This was to avoid split-package issues when working with Java modules.

However, testcontainers-kafka still suffers from split-package issues due to the deprecated org.testcontainers.containers.KafkaContainer class. This is in the org.testcontainers.containers package: a package which is also exported from the main testcontainers jar.

Relevant log output

error: module foo reads package org.testcontainers.containers from both testcontainers and testcontainers.kafka

Additional Information

The deprecated org.testcontainers.containers.KafkaContainer could have been dropped when moving to version 2.x. It should likely still be dropped now, as it will be causing people using modules pain.

It may also be worth considering adding a test to check from split packages across all modules in the repo. Otherwise, it's possible people will inadvertently reintroduce split package issues without realising.

[eddumelendez]

There are other issues pointing to this. See #7337

[big-andy-coates]

@eddumelendez seems like #7337 title and description is not related to the split package issue. Only comments added later. It's also tagged as resolution:somedaymaybe, which doesn't seem appropriate for the split-package issue users are encountering and which I figured was one of the driving forces behind the major version bump: moving things into their own non-split-packages.

Keep in mind that the split package issue doesn't just affect direct users of test containers, but also anyone using a library that uses test containers as a transient dependency.

Any chance this issue can be given some love? :)