Thanks Alan. A poor-man's solution may be optional module dependencies. Cheers, Paul
On Wed, Jan 13, 2016 at 11:08 AM, Alan Bateman <alan.bate...@oracle.com> wrote: > > On 13/01/2016 16:55, Paul Benedict wrote: > >> With multi-release JARs, there is a directory structure to partition out >> the class files for the destined versions of the Java runtime. >> >> With modules, the module-info.class sits in the root of the JAR. >> >> How will these two requirements be reconciled? Are there plans such as >> allowing module-info.class in each version folder too? It is quite >> conceivable a module will require dependencies in one Java version; yet >> not >> for another. >> > If dependences are significantly different then it might be pushing the > boundaries on multi-release JARs a bit. In any case, it is tracked as > JDK-8146486 to look at after JEP 238 has settled. > > -Alan > >
