First of all: This is not really an ebean issue, but maybe I can get some tips here, how to proceed.

We are using eclipse. Unfortunately with Ebean 13, the code base becomes incompatibe with eclipse
I think the main reason is JPMS / bad JPMS support in eclipse (and maybe also my lack of knowledge about JPMS)

Expected behavior

• run untitests from eclipse
• get no compile errors in eclipse

Actual behavior

• I cannot start unittests from eclipse at all (Can be fixed by adding
  --add-exports org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED
  and --add-exports org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED) I found that tip here https://www.edvpfau.de/junit5-debugging-mit-eclipse-und-gradle/
• If Unittest starts, it fails because I think, some module-infos are not yet correct (at least for tests. I did some modifications here: FOCONIS@e65d9bd, @rbygrave maybe you can check that)
• I get lots of compile erros as the test classes were not able to access the modules. For example:
  
  

Steps to reproduce

Checkout current master and import it in eclipse (Version 2022-03)

Note

Currently I run the tests in maven, but this makes it harder to debug (and it costs also more time)
I also noticed, that I get similar errors if I enable surefire.useModulePath in the POM file.
(Unfortunately I did not find this option in eclipse)