Based on feedback and further discussion, we're going with jdk.jpackager
and jdk.jpackager.runtime.
I’m also hoping that the service daemon support will make it into the JDK 12
deliverable. Is that out of the question at this point?
It won't make JDK 12, but is near the top of the list for JDK 13.
-- Kevin
On 11/1/2018 8:30 AM, Scott Palmer wrote:
On Oct 30, 2018, at 1:10 PM, Andy Herrick <andy.herr...@oracle.com> wrote:
On 10/30/2018 12:09 PM, Alan Bateman wrote:
...
Alex has suggested jdk.jpackager to avoid giving the impression that it's the "JDK
packager". Also several existing tool modules have the tool name in the module name
(jdk.jdeps, jdk.jlink, jdk.jshell, ...).
This seems reasonable, jdk.packager -> jdk.jpackager
still leaves the question of jdk.packager.services -> jdk.jpackager.services
(or jdk.jpackager.runtime) or something else ?
I prefer jdk.jpackager.runtime. I think it makes more sense given the likely
future functions that will be implemented there. User JVM args support and
single instance support don’t seem to fit the ’services’ name.
I’m also hoping that the service daemon support will make it into the JDK 12
deliverable. Is that out of the question at this point?
Regards,
Scott
