Jinq Roadmap

[Jinq]

In the past, I haven't had too much time to work on Jinq, so I've only been maintaining Jinq by updating the ASM dependency so that Jinq will mostly continue to work with newer versions of Java.

With the latest Java LTS release of JDK 17, I'm thinking of making a Jinq 2.0 release at some point. This release would have proper module support and would likely break compatibility with JDK8. I did some exploratory work on supporting modules earlier, and it seems like it would not be too much work. 

Oddly enough, the main thing holding me back from this change is that I can't figure out a good module naming scheme. I want to make separate modules for the internal implementation packages of Jinq. These internal modules need to be public because they are reused by the different hibernate and JPQL implementations of Jinq. But normal programmers don't need these internal classes clogging up their code completions in their IDEs, so I don't want them in the normal modules that normal programmers will use. I don't know what the convention is for naming modules. Should I just slap a public/internal/impl onto the module names as appropriate? Or is there a better convention?