On Sun, December 31, 2017 17:13, Remi Forax wrote: > jlink is not a distribution tool, you need to use a tool on top of jlink, > in the past, i've used the rpm format for that. > > We have stopped to distribute deltas when we have moved to docker that as > far as i know as no concept of incremental update. > > Rémi > > > ----- Mail original ----- > >> De: "Alan Bateman" <alan.bate...@oracle.com> >> À: "Thomas Brand" <t...@trellis.ch>, "jigsaw-dev" >> <jigsaw-dev@openjdk.java.net> >> Envoyé: Dimanche 31 Décembre 2017 16:55:37 >> Objet: Re: Update a runtime image >> > >> On 31/12/2017 15:42, Thomas Brand wrote: >> >>> Hello, I have a question related to jlink. >>> >>> >>> In a scenario where a runnable image created with jlink is installed, >>> and it should be updated, what are good strategies for doing this? >>> >>> I think if an update will introduce new dependencies this will be >>> different to updates that are known to be satisfied with what is >>> already in the image. >>> >>> The idea is to 'ship' just a small sort of diff / replacement part >>> that can be applied to the 'old' image to become 'new'. >>> >> The jlink tool always generates a new run-time image, there is no >> support at this time to install additional modules into a run-time >> image. >> >> -Alan. >>
Thanks for the facts & suggestions! Greetings
