there is an issue about how `module-info.java` wor...

# tornadofx

[alex]

there is an issue about how module-info.java works: there can not be two modules with the same package structure: i.e. typical main/com.foo/Test.kt and test/com.foo/TestForTest.jt will clash on com.foo and you can't have more than one module-info.java per project (IDE goes crazy about it).

The question boils down to where do you put requires org.junit.jupiter.api; (or whatever). It's rather strange to put such dependency in production module-info.java, yet you can't have separate module-info.java for test folder (without workarounds).

To understand better what I'm talking about, visit the link above, especially this post: https://sormuras.github.io/blog/2018-09-11-testing-in-the-modular-world
As far as I get it, this is one of the junit team members, but all of suggested methods looks crippled. That's why I'm asking, if whitebox testing is no longer possible (without hacks/tricks), and you need to create separate module for testing (with dedicated module-info.java and dependencies).