Closing out yet more open issues

David M. Lloyd david.lloyd at redhat.com
Wed Feb 15 22:57:51 UTC 2017


On 02/15/2017 04:29 PM, mark.reinhold at oracle.com wrote:
> Proposals for the following issues have been available for evaluation
> and experimentation for some time [1]:
>
>   #AwkwardStrongEncapsulation
>   #ClassFileAccModule
>   #ClassFileModuleName
>   #IndirectQualifiedReflectiveAccess
>   #ModuleNameCharacters
>   #NonHierarchicalLayers
>   #ReadabilityAddedByLayerCreator
>   #ReflectiveAccessToNonExportedTypes
>   #VersionedDependences
>
> Responses to these proposals have been either neutral or positive, and
> in some cases further suggestions have been adopted, so I've marked
> these issues as closed.
>
> We're still discussing the new constraints on module names included in
> the broader proposal for #VersionedDependences [2], but that's really
> an amendment to the accepted proposal for #VersionsInModuleNames [3],
> so I've closed the former issue and re-opened the latter.

The discussion around Layer#addPackage(Module, String) is presently 
under the heading of #NonHierarchicalLayers and I consider it unresolved 
as of yet.  Does it belong under a different issue?  The lines seem a 
bit blurred as discussion goes on.

-- 
- DML


More information about the jpms-spec-experts mailing list