On Thu, Feb 6, 2020 at 8:35 AM Christian Stein <sormu...@gmail.com> wrote:
> I agree with you, that the user (the build tool in most of the cases) > should > stay in control which module descriptor is in effect for every module. > > As my domain is testing, and I guess the majority of uses-cases is within > the realm of intra-module (white-box) testing, I'll expound on the topic > with > a complete example. > > > # GIVEN > > - src/foo/main/java/module-info.java > Reading this post a day later, I assume there more questions raised than answers given by this "foo" example. If that's the case, I apologize for the confusion -- my tunnel vision of "living on the testing side of the modular world" led to jumps in the story I wanted to tell. This time, I created a project at [0] with a detailed description on its front page, i.e the README.md file. I read that new story thrice and hope to have a more complete example prepared. It is based on the "Project Jigsaw: Module System Quick-Start Guide" [1] and extends the example modules with testing. Java-based build programs accompany the project to make it easy to "replay" (read: build) it on every supported platform. If any new questions appear, I'm happy to answer those on this ML. If you want me to copy "the new story" as plain text to this ML as well, just ping me. I refrained copying it directly, as it spans some pages and contains ASCII-art images, quotes, log excerpts... Cheers, Christian [0]: https://github.com/sormuras/java-module-patching [1]: https://openjdk.java.net/projects/jigsaw/quick-start
