----- Mail original ----- > De: "Sander Mak" <sander....@luminis.eu> > À: "jigsaw-dev" <jigsaw-dev@openjdk.java.net> > Envoyé: Jeudi 24 Novembre 2016 14:44:08 > Objet: Re: modules and tests
>> On 24 Nov 2016, at 14:31, Alan Bateman >> <alan.bate...@oracle.com<mailto:alan.bate...@oracle.com>> wrote: >> >> On 24/11/2016 08:46, Remi Forax wrote: >> >> : >> >> It's not obvious at it seems, it requires javac to be able to merge several >> module-info.java into one, and because the module descriptor allows to >> restrict >> exports or opens, the merging rules* as to be specified. >> >> Have you run into anything that isn't solved by compiling with >> -Xmodule:<module> >> and/or specify --add-reads and --add-exports to augment the module >> declaration? >> I realize it's awkward to specify these options but in time then I would >> expect >> the build tools and test runners to make this a lot easier. > > For a concrete example of this: > http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-March/006594.html > (modulo the old-style flags). Later I ported the same example to the a Maven > build, which takes care of all this setup under the hood. Worked fine, without > having to fiddle with -Xmodule/-Xpatch and readability to test-scope > dependencies happens automatically in that case. > > > Sander to Alan: currently you can not get your test framework as a service and you can not declare your test as a provider for a test infrastructure like jenkins (i.e. there is no --uses and --provides). to Alan and Sander: setting command line arguments or using a build tool to fiddle them for you is exactly what we do not want here! We want fidelity between the compile time configuration and the runtime configuration. Having to play with -Xpatch at runtime is conceptually exactly like setting the classpath. I don't want to explain to the Java devs that we have fidelity between compile-time and runtime on source code but not on test code. regards, Rémi
