For "requires static" specifically, this effect is quite dramatic since it makes the optional runtime dependency feature useless for a large number of target scenarios.
Alright, I'll re-test against build 156+ then. Juergen On Fri, Feb 3, 2017 at 8:07 PM, Alan Bateman <alan.bate...@oracle.com> wrote: > On 03/02/2017 18:14, Juergen Hoeller wrote: > > : >> >> Was it intentional for "requires static" to work that way? Am I missing >> something? From my perspective, "requires static" means that the >> referenced >> module has to be present when compiling the declaring module... but not >> when compiling other modules depending on the declaring module. >> >> I suspect what you are seeing isn't specific to `requires static` but > rather a long standing issues where javac has needed the transitive closure > to be observable when compiling any module. There are changes in jdk9/dev > for jdk-9+156 (next week's build) that mostly fix this issue and it will > be interesting to see if that addresses your concerns. > > -Alan >
