On 10/01/2018 17:39, Gunnar Morling wrote:
:
What exactly do you mean by "broken app module"? It was my
understanding that by applying that exclusion pattern, no trace
whatsoever of the app module would end up in the resulting runtime
image. If I run /bin/java --list-modules it's not shown in
2018-01-10 16:28 GMT+01:00 Alan Bateman :
> On 10/01/2018 10:32, Gunnar Morling wrote:
>
>> Hi Thomas,
>>
>> What I've found helpful is the ability to amend or override the set of
>> modules contained in a modular runtime image via --module-path and
>> --upgrade-module-path.
>>
>> If you use (Dock
On 10/01/2018 10:32, Gunnar Morling wrote:
Hi Thomas,
What I've found helpful is the ability to amend or override the set of
modules contained in a modular runtime image via --module-path and
--upgrade-module-path.
If you use (Docker) containers to deploy your app, this can be employed
nicely t
; >> De: "Alan Bateman"
> >> À: "Thomas Brand" , "jigsaw-dev"
> >>
> >> Envoyé: Dimanche 31 Décembre 2017 16:55:37
> >> Objet: Re: Update a runtime image
> >>
> >
> >> On 31/12/2017 15:42, Thomas Br
now as no concept of incremental update.
>
> Rémi
>
>
> - Mail original -
>
>> De: "Alan Bateman"
>> À: "Thomas Brand" , "jigsaw-dev"
>>
>> Envoyé: Dimanche 31 Décembre 2017 16:55:37
>> Objet: Re: Update a runtime image
e: "Alan Bateman"
> À: "Thomas Brand" , "jigsaw-dev"
>
> 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
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
differen
