"javapackager" in no-mans-land?
johan.vos at gluonhq.com
Mon Sep 24 06:14:56 UTC 2018
Auto-update and a packager are different things.
Both are needed, but at this moment, there is only a JEP for the packager.
I think it would be wise to have a standard (hence a JEP) for auto-update
as well, as the use case you describe is not unique...
On Sun, Sep 23, 2018 at 8:40 AM Kamlesh Prajapati
<kamlesh.prajapati at hops.healthcare> wrote:
> Thanks for your replay.
> I found exe build using maven with 'javafx-maven-plugin' Or Inno Setup tool
> but My project is update release every 2 week. so auto update tool for
> manage inside client system.
> Also i found auto update tool Like
> But which is long term support with all java update.
> On Fri, Sep 21, 2018 at 2:59 AM Kevin Rushforth <
> kevin.rushforth at oracle.com>
> > On 9/20/2018 12:05 PM, Kamlesh Prajapati wrote:
> > > Currently , I used javafx 8 with JNLP Application.
> > >
> > > Is JNLP application support in javafx11 + java11 ?
> > The deployment stack, including Java Web Start and Applet support, has
> > been removed from JDK 11. You will either need to find an alternative to
> > Java Web Start or keep your application on JDK 8. Packaging your
> > application with the JDK might be an alternative to Java Web Start. If
> > so, the new jpackager tool could help you, in which case an interim
> > solution would be to use use the javapackager, either the one from JDK
> > 10 or an unbundled javapackager, as suggested by others.
> > > Any idea about auto update application in win(exe),mac,linux base
> > > application ?
> > Auto-update is something the application would need to provide.
> > -- Kevin
> Thanks With Regards,
> Kamlesh Prajapati
More information about the openjfx-dev