On 05/12/2014 17:57, Sergey Bylokhov wrote:
On 04.12.2014 20:11, Alan Bateman wrote:
We've now moved to world where the runtime images are created from a
set of modules and this should give a lot of flexibility once. We're
just not there yet with locale data so we have to temporarily link in
On 04.12.2014 20:11, Alan Bateman wrote:
We've now moved to world where the runtime images are created from a
set of modules and this should give a lot of flexibility once. We're
just not there yet with locale data so we have to temporarily link in
the big jdk.localedata module so that the
On 04/12/2014 12:58, Xerxes Rånby wrote:
The footprint of the compact profiles have been inflated by ~12Mb each
after the JEP 220 changes.
before
# du -s -h j2re-compact1-image
17.9Mj2re-compact1-image
# du -s -h j2re-compact2-image
28.7Mj2re-compact2-image
# du -s -h
Quick question. Why is jdk.localedata module included in the compact
profiles? The data there used to be in lib/ext/localedata.jar and
lib/ext/cldrdata.jar which weren't included in those compact profiles.
Naoto
On 12/4/14, 5:48 AM, Alan Bateman wrote:
On 04/12/2014 12:58, Xerxes Rånby
On 04/12/2014 16:38, Naoto Sato wrote:
Quick question. Why is jdk.localedata module included in the compact
profiles? The data there used to be in lib/ext/localedata.jar and
lib/ext/cldrdata.jar which weren't included in those compact profiles.
Naoto
The profiles make target on JDK 8 (and JDK
