Open remal opened 5 years ago
As far as I understand it, we would solve this issue once we solve #1523, correct?
@kiview , unfortunately no. It requires some refactoring that will break backward compatibility. JPMS requires modules not to share same packages. In other words if a module has classes within package a.b.c
no other module can have classes within the package. But other module can have classes within subpackages like a.b.c.d
.
@rnorth Can we have this issue fixed in 2.0?
BTW I can help by submitting a PR, but there should be some maintainers' decision, as the PR will break backward compatibility.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.
The issue is still actual
Is there any decisions/updates on this issue?
Years later, and unfortunately testcontainers still does not support modern Java (that use JMPS - modules). What a shame!
The error:
I have a JPMS project with
module-info.java
file. And I have split package issue when I'm trying to compile the project.Java 8 public support ends in 2020. It's pretty soon. IMHO it makes sense to start developing Testcontainers using newer version of Java and targeting Java 8 bytecode.