----- Mail original ----- > De: "Alan Bateman" <alan.bate...@oracle.com> > À: "Cédric Champeau" <cedric.champ...@gmail.com> > Cc: "jigsaw-dev" <jigsaw-dev@openjdk.java.net> > Envoyé: Mardi 27 Mars 2018 10:29:36 > Objet: Re: The baby and the bathwater
> On 27/03/2018 08:15, Cédric Champeau wrote: >> Dual testing is a minimum. In practice, it depends on the kind of tests. >> Typically, before JDK 9 for unit tests you never needed a jar to execute >> unit tests. Maven happens to built it, but in practice a class directory + >> resources is enough > This hasn't changed. You can put directories containing the test classes > + resources on the class path as before. When testing modules you can > patch a module to add the test classes (and resources) that are compiled > into a directory, no need for either the module or the tests to be > packaged as JAR files. with the limitation that you can not patch a module-info so if you have testing-only dependencies like JUnit and you want to run them in module-mode, you have to generate a jar. > > Maybe your comment is about testing libraries that are Multi-Release JARs? > > -Alan. Rémi
