Closed koppor closed 4 years ago
I think the jar files are obsolete (also the ones from the libraries) as they all should be included in the lib/modules file...
The other size info was http://builds.jabref.org/chocoDev/:
Largest difference - as we discussed. Will remove them at https://github.com/JabRef/jabref/pull/5748
Reading the badass jlink link doc:
The badass-jlink plugin takes a more pragmatic approach by combining all non-modular dependencies into a single jar. This way, only the resulting merged module needs a module descriptor.
I interpret this as that the merged module is required somehow. However, I tried to start the portable zip where this was removed (source: http://builds.jabref.org/change-upload-back-to-script/) and it worked. Strange.
It's probably related to https://github.com/beryx/badass-jlink-plugin/issues/51. I would recommend to remove these files as part of https://github.com/JabRef/jabref/blob/5ffb1b2924691f132b578c86123248fe3355e3a7/build.gradle#L699
I would assume
jpackageImage
creates the .deb
, .msi
, .pkg
filesjpackageImage
includes the app/mods
folderdeleteModsFolder
runs afterWhich assumption is wrong?
The first. jpackageImage creates the so-called application image, which contains everything you need to run JabRef (distribution/JabRef). The installer are created afterwards in jpackageInstaller (or something similar named).
Nonetheless, there appears to be a problem as the mods folder is never deleted, right?
There is a bug report for jpackage: https://bugs.openjdk.java.net/browse/JDK-8236830
Guess who reported it :smile:
Try quick shot by deleting mods
folder. IF not succeed, take out of v5.1.
Idea:
gradle jPackage
locally.sh
locally to testShould be fixed now.
(I did not find the issue. Feel free to link the issue and close this one)
Our installer size decreased. I quickly looked into it and foudn following two files:
Do we really need
JabRef.merged.module-....jar
?We also have lib/runtime/lib/modules with 157MB of size. Are the modules doubled here?