Draft JPMS EDR specification
Remi Forax
forax at univ-mlv.fr
Sat Dec 24 13:34:02 UTC 2016
s/now/not
Rémi
----- Mail original -----
> De: "Remi Forax" <forax at univ-mlv.fr>
> À: "mark reinhold" <mark.reinhold at oracle.com>
> Cc: jpms-spec-experts at openjdk.java.net
> Envoyé: Samedi 24 Décembre 2016 13:53:22
> Objet: Re: Draft JPMS EDR specification
> Minor nit,
> in the VM spec part, section 2.1, the attribute ModuleVersion is mentioned while
> it has disappeared
> (the module version is now a field of the Module attribute).
>
> I will modify ASM next week to be in sync with the spec, i do not expect any
> problems.
>
> I still think that encoding a version for the requires inside the Module
> attribute is now a good idea (cf my previous message).
>
> Happy Christmas everyone,
> Rémi
>
> ----- Mail original -----
>> De: "mark reinhold" <mark.reinhold at oracle.com>
>> À: jpms-spec-experts at openjdk.java.net
>> Envoyé: Mercredi 21 Décembre 2016 22:12:16
>> Objet: Draft JPMS EDR specification
>
>> I've posted a draft EDR specification for your review, here:
>>
>> http://cr.openjdk.java.net/~mr/jigsaw/spec/
>>
>> This document gathers the collected changes proposed for the JLS, the
>> JVMS, the Java SE API, and various low-level interfaces (JNI, JVM TI,
>> and JDWP).
>>
>> The intent of the EDR is to provide a comprehensive snapshot of our work
>> to JCP participants who do not follow our activity closely. It by no
>> means implies that we are finished -- we'll continue to work through the
>> issues already identified, and on issues raised by feedback yet to come.
>>
>> I plan to submit this to the PMO as the Early Draft Review Specification
>> on 10 January. Please let me know by 17:00 UTC on Monday, 9 January if
>> you think any changes are required, or if you need more time for review.
>>
> > - Mark
More information about the jpms-spec-observers
mailing list