First step: use define automatic modules module names (no module-info) and restore the tests with java modules that we had in Search 5. These tests, obviously, will only be executed when building with JDK9+.
Second step: add a JDK11+ Maven profile to our POM ({{-Pmodule-descriptors}} with all the necessary configuration so that our POM defines module-info files. Check that when building with JDK11+, those module-info files are actually used by the java module tests we added in step 1. If everything works (I doubt it will), enable that profile by default on JDK11+, so that we test it regularly in the CI.
The goal is NOT to define full module-info descriptor for consumption by our users: we will just test that it seems to work. We do not currently want to switch to JDK11 for our release build, so we simply cannot define module-info descriptors for now. |
|
