java.mini? was: Dependency leaks and embedded Java
Alan Bateman
Alan.Bateman at oracle.com
Tue Oct 23 02:01:37 PDT 2012
On 23/10/2012 08:10, Jaroslav Tulach wrote:
> :
>
> A modularization has to be driven by a need, I know. So far the only need
> jigsaw team tried to achieve was to fit Hotspot on mobile devices and for that
> java.base is enough (as demonstrated @ J1).
>
> However for certain environments it is clearly to big. Can't jigsaw also define
> the smallest possible profile (e.g. with classes that are directly needed
> during compilation by Javac like String, StringBuilder, Enum, Throwable)?
>
> Having such "java.mini" profile would help porting Java to unusual small
> environments. It would ultimately lead to smaller fragmentation of Java - as
> it is better if the smallest profile is standardized than created by
> independent individuals.
>
Right, the convergence effort is focused at Java SE / Java ME CDC rather
than the much smaller environments that have been the focus of the CLDC
and JavaCard specifications.
Bob Vandette's slides from JavaOne 2012 provides up to date information
on the current efforts and the footprint goals for JDK 8:
https://oracleus.activeevents.com/connect/fileDownload/session/CDC887FAEAD8ABE54064406AC304AD59/CON4538_Vandette.pdf
-Alan.
More information about the jigsaw-dev
mailing list