Jigsaw delayed

[Daniel Zwolenski]

That's good to hear. I hope the legal side of this will be included in this work so that end developers can do this manual modularisation as well. I believe currently the legals prevent us from stripping out most of the bits of a jre even for cobundling (or so I've been told).

Awesome scenario would be to have a stripped minimal jre available for download as a zip and then all the other jars/dlls available for manual inclusion. Ie opt in, rather than opt out. 

I'm guessing this is outside the jfx teams realm of influence but just thought I'd mention it in case it comes up at office pizza night or the like ;)



On 26/07/2012, at 7:16 AM, Richard Bair <richard.bair at oracle.com> wrote:

> Actually we're going to continue to work on modularization, only we'll be doing it "the old fashioned way" rather than using JigSaw for JavaFX. So for example we can still strip / subset classes / jars. We just won't get the fancy JigSaw for doing the modularization.
> 
> We've gotta have it for embedded and such in any case.
> 
> Richard
> 
> On Jul 25, 2012, at 2:05 PM, Daniel Zwolenski wrote:
> 
>> Unfortunately it looks like Jigsaw (Java modularisation) is being pushed from Java 8 to Java 9, which means it is at least three years away. 
>> 
>> http://mreinhold.org/blog/late-for-the-train
>> 
>> This means co-bundling and AU will be stuck with large JRE downloads for a while yet unfortunately. 
>> 
>> I'm wondering of any other proposed JFX features are likely to be affected by this. In particular would the hypothetical, whispered mobile support be dependent on Jigsaw or could it theoretically move ahead anyway?
>> 
>> Cheers,
>> Dan
>> 
>> 
>> 
> 
>