How to avoid uploading the full .jar file on every update

I am facing a little issue while deploying a new version of any of my Spring boot Apps.
A .jar file containing some basic Spring boot dependencies can easily reach 80Mo, which is not a big problem but still becomes annoying when deployment is frequent or when connection speed degrades for some reason.
No matter how minor the change is, the whole new .jar must be uploaded even if 99.999% of it is the same as the previous one.

Generating the .jar in the production doesn’t seem to be ideal.

The goal is to be able to update the Apps with the minimum transferred data. How can this goal be achieved?

You need to sign in to view this answers