Optional framework dependencies: requires static vs automatic modules
Alan.Bateman at oracle.com
Fri Feb 3 19:07:44 UTC 2017
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.
More information about the jigsaw-dev