RFR: JDK-8212780: JEP 343: Packaging Tool Implementation
Alan.Bateman at oracle.com
Tue Oct 30 16:09:25 UTC 2018
On 30/10/2018 14:11, Andy Herrick wrote:
>> What is the status of the JNLPConverter tool? I see it is included as
>> a "demo" but maybe it would be better to host somewhere else as this
>> is for developers migrating Java Web Start applications.
> Our current plan is to deliver it only as a demo.
This looks like a migration tool rather than a demo so not clear to me
that this is the right approach. Also as the tool is for migration from
Java Web Start when maybe it should be a tool hosted with the Oracle JDK
download rather than something to put into the JDK.
>> If I read the webrev correctly then it adds two modules, one with the
>> jpackager tool and the other with an API. It would be useful to get a
>> bit more information on the split. Also I think the name of the API
>> module and the package that it exports needs discussion to make sure
>> that the right names are chosen.
> Yes - though we are currently using jdk.packager.services, we are open
> to other suggestions as the name for these. "jdk.packager.runtime" has
> also been suggested.
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, ...).
Is the API to ensure that only one instance of the application is
running really tied to the jpackager tool? Could it be used by
applications that aren't packaged in with this tool? I'm asking in case
there is a better name for this API module.
More information about the core-libs-dev