#AddExportsInManifest

[Paul Bakker]

Hi Alan,

What is the reason only exports/opens to unnamed are possible?
Also, are these implemented in the current jigsaw prototype? I'm having trouble getting it to work, but that might be entirely my own doing...

Thanks,

Paul

> On May 10, 2017, at 11:39 PM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
> 
> On 11/05/2017 07:22, Paul Bakker wrote:
> 
>> Hi all,
>> 
>> In #AddExportsInManifest two new manifest entries are proposed. I can only find the following email containing more details: http://mail.openjdk.java.net/pipermail/jpms-spec-observers/2016-September/000547.html <http://mail.openjdk.java.net/pipermail/jpms-spec-observers/2016-September/000547.html>.
>> Is this still current? I'm trying this in an example, but it doesn't seem to have any effect. Also, is the Add-Exports-Private replaced by Add-Opens?
>> 
>> The proposal only speaks about exporting to unnamed modules. Is it also possible to export to other modules? E.g. 'Add-Exports: m/p=othermodule?
>> 
> The attributes names are "Add-Exports" and "Add-Opens". JEP 261 needs a big update and one of the things needed is to document these attributes in the JEP (as they are JDK-specific attributes rather than attributes for the JAR file spec).
> 
> As the attributes are for executable JAR files only then the effect is to export or opens the packages to unnamed modules only (so no `=<target-module>` in the value).
> 
> -Alan