[jsr294-modularity-eg] JSR 294 expert group draft
bryan.atsatt at oracle.com
Mon Oct 22 13:17:30 EDT 2007
I haven't yet had time to review these, but... Does this draft address
the runtime class generation issue?
Andreas Sterbenz wrote:
> [My earlier mail seems to have been lost, resending...]
> reminder to send us your comments about the draft spec by next Monday
> October 29. After this expert group review, we should proceed to JCP
> Early Draft Review so that we can gather feedback from the larger
> Andreas Sterbenz wrote:
>> based on our earlier discussions Alex and I have prepared a draft
>> specification for Superpackages. It consists of updates to the Java
>> Language Specification, the Java Virtual Machine Specification, and
>> the reflection API.
>> The specification reflects our past discussions in the EG, except in
>> a few cases where we are suggesting changes based on our experience
>> in the prototype implementation. For example, we changed the proposed
>> name of the compiled superpackage file from super-package.spkg to
>> super-package.class. That should avoid some tool compatibility issues
>> and makes more sense given our later decision about the file format.
>> We have also allowed a Java source file (compilation unit) to
>> optionally identify which superpackage its types are in. There are
>> some minor updates to the reflective API: the addition of
>> SuperpackageFormatError and the method Superpackage.forName().
>> You can find the documents on the EG page,
>> http://jcp.org/en/eg/view?id=294 . We believe these drafts can serve
>> as the basis for the JCP Early Draft Review.
>> We would appreciate if you could send us your comments by Monday,
>> October 29.
>> Alex and Andreas.
>> jsr294-modularity-eg mailing list
>> jsr294-modularity-eg at cs.oswego.edu
More information about the jsr294-modularity-eg