[jsr294-modularity-eg] January 2010 - and those open questions
Alex.Buckley at Sun.COM
Sat Jan 30 18:15:28 EST 2010
With great respect, the Expert Group does not answer to observers.
As spec lead, I answer to the SE/EE Executive Committee of the JCP, to
whom I presented 294's direction a couple of weeks ago.
The EG is currently considering a draft spec intended for EDR. I sent
the material in December to the private EG list in the first instance,
as has always been the custom. A number of comments have recently been
made on that list, which I will consider before initiating the EDR. I do
not intend to send the material to the observer list ahead of the EDR,
since it is supposed to be the EDR that kickstarts community review.
Stephen J. McConnell wrote:
> If I were feeling cynical I could suggest that I just love the way that
> expert group members jump in and express opinions. I could perhaps
> suggests that it makes me feel all warm inside. Problem is that I'm not
> cynical and I'm not feeling all warm and fuzzy.
> So perhaps I need to lay out some direct questions:
> a) where is the specification
> b) where is the expert group
> Cheers, Steve.
> On Thu, 2010-01-28 at 23:02 +1030, Stephen J. McConnell wrote:
>> What is the status on this (re. your comments below)?
>> A timeline would be great.
>> Cheers, Steve.
>> On Fri, 2009-12-11 at 09:15 -0800, Alex Buckley wrote:
>>> So, I will file an EDR this month based on the materials from June,
>>> along the following lines:
>>> - Module accessibility is a JLS concept; runtime module is a JVMS
>>> - Module compilation unit is a JLS concept; it defines a module name
>>> version; it is annotatable; its contents are implementation-defined.
>>> - java.* APIs are limited to representing runtime modules and (the
>>> runtime form of) module compilation units.
More information about the jsr294-modularity-eg