Igor Nekrestyanov wrote:
Let me clarify this as it is does not directly translate into 3x
footprint.
But savings are not just "size of classes to be loaded".
Common "core" classes are also included into shared archive
(classes.jsa) and removing logging classes
from the "core" will reduce siz
Mandy Chung wrote:
(I took the core-libs-dev off as this is about awt/2d/swing discussion).
The main question is whether the client stack wants to require the
dependency on logging when the JDK is broken down into fine-grained
module. It is fine to wait until the jigsaw module system is read
Let me clarify this as it is does not directly translate into 3x footprint.
But savings are not just "size of classes to be loaded".
Common "core" classes are also included into shared archive
(classes.jsa) and removing logging classes
from the "core" will reduce size of classes.jsa (which is m
BTW, note that reducing set of required core classes will save 3x of
memory at least (think of jqs and classes.jsa in addition to rt.jar (on
windows)).
-igor
On 9/22/09 10:19 AM, Mandy Chung wrote:
(I took the core-libs-dev off as this is about awt/2d/swing discussion).
The main question is
(I took the core-libs-dev off as this is about awt/2d/swing discussion).
The main question is whether the client stack wants to require the
dependency on logging when the JDK is broken down into fine-grained
module. It is fine to wait until the jigsaw module system is ready to
provide the pe
