Re: RFR [9] 8168149: Examine the behavior of jmod command-line options - repeating vs last one wins

> On Dec 22, 2016, at 9:11 AM, Chris Hegarty wrote: > > Most options for the jmod tool should be last one wins, to be consistent > with the JDK tool convention, 8168149 [1]. Excludes is the only > repeatable option. > > Given the existing usage of JOpt Simple, the

Compiling Java 9 (take 2)

I have started to dig through the JLS changes (2016-12-16) to figure out requirements for a Java 9 compiler without consulting javac, but I'm having some difficulties understanding the interplay of scope, visibility, importing, accessibility and observability at this level. For instance, this

Re: Proposed enhancement to Layer API

On 01/04/2017 08:26 AM, Alan Bateman wrote: On 04/01/2017 14:21, David M. Lloyd wrote: We need the ability to add content to a module after it is defined to support our existing deployment architecture. Is there a material problem with having this feature, other than transgressing your sense

Re: Proposed enhancement to Layer API

On 04/01/2017 14:21, David M. Lloyd wrote: We need the ability to add content to a module after it is defined to support our existing deployment architecture. Is there a material problem with having this feature, other than transgressing your sense of "should"? Can you expand a bit on this?

Re: Proposed enhancement to Layer API

We need the ability to add content to a module after it is defined to support our existing deployment architecture. Is there a material problem with having this feature, other than transgressing your sense of "should"? On 01/03/2017 05:33 PM, Remi Forax wrote: I agree with all the proposed

Java 9/jigsaw slides

Folks, Brian recommended that I speak at the Philly Emerging Tech conference and they would like a talk about Java 9, with some hints of future plans. Do any of you have slides you would recommend that I could use as a starter set? thanks, Karen