Before we get to far off the intention of this discussion, let's refocus. The purpose of the this discussion isn’t to find the “best” modules solution but rather to find one that is “good enough” to allow Geode 1.x to work in a Java 11 world with a reasonable user experience. While we can run the server effectively in Java 11 we cannot consume modules nor be consumed as modules by a modularized Java 11 application. Whatever steps we take in Geode 1.x will likely be thrown away for a solid solution for 2.x.
So the question is: 1) Is refactoring internal to avoid the split packaging issue have a significant negative impact on downstream projects that currently use internal classes due to deficiencies in our public APIs? If so, what are the impacts and can we minimize them in other ways? 2) Would an uber module be a safer and less negatively impactful solution than option 1? 3) Is there some other interim solution nobody has thrown out yet? -Jake
