On 11/18/19 4:34 AM, Alan Bateman wrote:
This issue concerns the interaction of service binding with incubator
modules, a left over from JDK 9 that resurfaces with the upcoming JEP
343 Packaging Tool (Incubator).
The summary on this issue is that service binding augments the module
graph
On 11/18/2019 11:10 AM, Alan Bateman wrote:
We could potentially say something about tools that are incubator
modules here. The launcher for the tool, "jpackage" in the case of JEP
343, will use the name of the incubator module as the root module to
resolve.
I updated JEP 11 to allude to incu
On 18/11/2019 17:54, Alex Buckley wrote:
An incubator module's service providers will now be unavailable by
default even if a module on the module path says `uses`. I believe
that JEP 11 should say the following:
-
Incubator modules are part of the JDK run-time image produced by the
stand
On 11/18/2019 4:34 AM, Alan Bateman wrote:
The summary on this issue is that service binding augments the
module graph with the modules induced by the service-use relation.
... If service binding were to resolve `jdk.incubator.jpackage` > then a
warning would be emitted in all phases that java.
This issue concerns the interaction of service binding with incubator
modules, a left over from JDK 9 that resurfaces with the upcoming JEP
343 Packaging Tool (Incubator).
The summary on this issue is that service binding augments the module
graph with the modules induced by the service-use
