[CC JPMS expert mailing list because, it's an important issue IMO]
I've a counter proposition.
I do not like your proposal because from the user point of view, '^' looks like
a hack, it's not used anywhere else in the grammar.
I agree that restricted keywords are not properly specified in JLS.
Regarding previous comments about not wanting to support such an extension of
what are viewed as internal APIs, these proposed extensions could be guarded by
a command line option such as --enable-jpms-experimental-api that carries
warning messages along the lines of the --permit-illegal-access
I've proposed five patches to the jpms-spec-experts list [1..5] for
discussion. The patches are as follows:
1. Layer primitive: addExports() - mirrors the existing
Module.addExports() method for ModuleLayer.Controllers
2. Layer primitive: addUses() - mirrors the existing Module.addUses()
meth
compiler-dev is the right list to query javac's behavior.
Support for private methods in interfaces came via JEP 213, and it
sounds like you're saying private fields are allowed accidentally.
Please give example source code when you write to compiler-dev.
Alex
On 5/11/2017 3:45 PM, Ess Kay w
(This is not a jigsaw specific specific question but I could not find
a more appropriate mailing list. The COIN list is archived. If there
is a a more appropriate mailing list then please let me know.)
The Java 9 compiler currently allows
1) private static and instance fields and
2) non-final sta
Hi Kevin,
On 05/10/2017 03:19 AM, Kevin Rushforth wrote:
inline
Peter Levart wrote:
Hi Kevin,
On 05/02/2017 02:21 AM, Kevin Rushforth wrote:
This review is being cross-posted to both openjfx-dev and jigsaw-dev.
Please review the proposed fix for:
https://bugs.openjdk.java.net/browse/JDK-81
These two attributes are defined to ease migration so that executable JARs can
run with java -jar command, as is today, to avoid adding command-line options
to break into encapsulation.
Mandy
[1] http://openjdk.java.net/projects/jigsaw/spec/issues/#AddExportsInManifest
> On May 11, 2017, at 1:2
I'm a little confused by "...deployments work if they are dependent on JDK
internal APIs". What does internal JDK usage have to do with opening/exporting
your own packages? I would think this solves the problem that some other code
(e.g. a library) requires access to application code?
Also, can
On 11/05/2017 07:51, Paul Bakker wrote:
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...
The attributes are defined for the mai
