Another temporary javac hack please
mr at sun.com
Mon May 18 09:20:20 PDT 2009
> Date: Mon, 18 May 2009 08:05:30 -0700
> From: jonathan.gibbons at sun.com
> As a short term hack, I can do this, but longer term I still think we
> need a better way of recognizing names which identify platform
> modules., either using modifiers or a more general naming scheme
> that allows for different types of the platform (meaning versions in
> the sense of Java ME, Java SE, etc.
Couldn't agree more. To do this right, however, requires implementing
"provides" clauses first, and that's unlikely to happen in the next
two weeks. Modules named "jdk(\.\w+)?" are ultimately intended merely
to be artifacts of our implementation; applications, if they declare
an explicit platform dependence, will refer to abstract modules named
"java(\.\w+)?". We will actively, and perhaps mechanically, discourage
people from referring to "jdk" modules.
In the meantime, org.openjdk.jigsaw.Platform.isPlatformModuleName(String)
will tell you what is, and is not, a "platform" module.
> As a right now hack, you could put an empty module-info.java
> with the right name on your compilation module path.
Yes, but for demo purposes I'm mainly using single-module source and
classes directories, in the traditional layout.
More information about the jigsaw-dev