-
-
Notifications
You must be signed in to change notification settings - Fork 64
Description
Testing Problem
When adopting the Java Platform Module System in your application, you explicitly list which modules are required to build your application successfully.
When using jqwik's standard features, it is sufficient to require only the net.jqwik.api module which is provided by the net.jqwik:jqwik-api artefact.
However when you need features from one of jqwik's submodules (time, web or engine), you have to require net.jqwik.engine module. However, this displays an Ambiguous Module Reference error as the module is provided by all 3 submodules instead of only one. This makes the functionality of the submodules not usable in combination with the Java Platform Module System.
Suggested Solution
In the build.gradle files of the mentioned submodules, the jar task explicitly adds an automatic module name. This is, however, only correct for the engine submodule and should be corrected in the other two.