Given the circular 'we at a dead-lock' type posts I see on the modularity EG list (well, the observer list anyway) I get the feeling that it'll be a LONG time since we see modularity in the JDK. And if we do happen to see it for Java 7 - there's likely to be a lot of disgruntled/frustrated people over it 'not going there way'. I certainly hope a proposal and solution come up soon that keeps everyone happy - although at this late stage in the game, even once they get a solution and have it implemented, theres the mammoth task of actually modularising the JDK codebase, and the even bigger wooly mammoth task of decided how granular those modules should be.
I really don't envy Alex, Joe and anyone working on that task. OSGi and my relatively small project is enough for my headaches :) Mark -- Pull me down under... On Wed, Sep 30, 2009 at 5:37 AM, Serge Boulay <serge.bou...@gmail.com>wrote: > What I got out of the podcast was that each jdk has a some sort of > priorty/theme. For jdk 7, it’s modularity. Like any other business resources > are allocated based on achieving that priority. Modularity is the major > change > for jdk 7 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
