Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decrease size of distribution #5771

Closed
koppor opened this issue Dec 20, 2019 · 13 comments
Closed

Decrease size of distribution #5771

koppor opened this issue Dec 20, 2019 · 13 comments
Assignees
Milestone

Comments

@koppor
Copy link
Member

koppor commented Dec 20, 2019

(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:

grafik

Do we really need JabRef.merged.module-....jar?

We also have lib/runtime/lib/modules with 157MB of size. Are the modules doubled here?

@tobiasdiez
Copy link
Member

I think the jar files are obsolete (also the ones from the libraries) as they all should be included in the lib/modules file...

@koppor
Copy link
Member Author

koppor commented Dec 20, 2019

The other size info was http://builds.jabref.org/chocoDev/:

grafik

@koppor
Copy link
Member Author

koppor commented Dec 20, 2019

Largest difference - as we discussed. Will remove them at #5748

  • grafik
  • grafik
  • grafik

@koppor
Copy link
Member Author

koppor commented Dec 21, 2019

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.

@tobiasdiez
Copy link
Member

It's probably related to beryx/badass-jlink-plugin#51. I would recommend to remove these files as part of

task deleteModsFolder(type: Delete) {

@koppor
Copy link
Member Author

koppor commented Dec 21, 2019

Windows

grafik

Linux

grafik

Mac

grafik

@koppor
Copy link
Member Author

koppor commented Dec 21, 2019

I would assume

  • jpackageImage creates the .deb, .msi, .pkg files
  • jpackageImage includes the app/mods folder
  • deleteModsFolder runs after

Which assumption is wrong?

@tobiasdiez
Copy link
Member

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?

@koppor koppor self-assigned this Jan 9, 2020
@Siedlerchr
Copy link
Member

There is a bug report for jpackage: https://bugs.openjdk.java.net/browse/JDK-8236830

@tobiasdiez
Copy link
Member

Guess who reported it 😄

@tobiasdiez tobiasdiez modified the milestones: v5.0, v5.1 Feb 23, 2020
@koppor
Copy link
Member Author

koppor commented Apr 14, 2020

Try quick shot by deleting mods folder. IF not succeed, take out of v5.1.

@koppor
Copy link
Member Author

koppor commented May 12, 2020

Idea:

  • run gradle jPackage locally
  • create .sh locally to test
  • code and fix
  • copy back script commands to build file
  • Alternative: register as gradle task and remove files before archive is created
  • Good documentation of jlink https://badass-jlink-plugin.beryx.org/releases/latest/

@koppor
Copy link
Member Author

koppor commented Jul 27, 2020

Should be fixed now.

@koppor koppor closed this as completed Jul 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants