Hi Mandy,
On 17/01/2017 7:51 AM, Mandy Chung wrote:
java.compact$N modules were removed in jdk-9+150 [1][2].
We revisited the need for java.compact$N aggregator. Compact Profiles
were useful in SE 8 but are legacy in 9, as intended from the outset.
Highlighting them in the standard SE 9 module graph gives them
unnecessary importance going forward. We want people who care about
small systems to think about modules, not profiles.
I would assume however that we will clearly document how to go from a
compact profile to using jlink to produce a comparable JRE? At a
minimum, given the compact profiles were defined at the package-level,
we should document which modules are needed to provide the packages
defined for a given compact profile.
In addition, these aggregator modules are not a complete solution
since the necessary service providers are still needed to be added
manually for the Compact Profile builds.
That sounds like it also needs further explanatory documentation.
Thanks,
David
Mandy
[1] https://bugs.openjdk.java.net/browse/JDK-8171201
[2] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-December/010561.html
On Jan 16, 2017, at 1:35 PM, Sander Mak <[email protected]> wrote:
The build I'm currently using (jigsaw-b151) doesn't contain the java.compactN
modules anymore. Looks like this is a deliberate removal [1], although I can't
find any reason for it. Are they permanently gone? Why? They made for such a
nice example of implied readability in the JDK... They were also useful in
constructing small images with jlink. As I understood things at JavaOne, jlink
with the compact module definitions was supposed to be a 'migration path' from
Java SE 8 embedded.
Sander
[1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-December/010603.html
