JavaPackager | Maven plugin to package Java applications | DevOps library

Does anyone know what the * following a filename in macOS terminal means?

All the file names in the folder:

/System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands

have a * trailing them and I'm not sure why.

For example:

I package a JavaFX application using maven and OpenJDK 1.8 The relevant part from my pom.xml:

I have JavaFx ShowTime.jar and config folder. To run the software, the config folder needs to be in a same directory as ShowTime.jar. In side the config folder, there are two folders : preferences and plugins.

I can bundle the config folder with the jar using the following codes:

when we create jlink runtime images we can use tags such as '--strip-debug', '--compress', '2', '--no-header-files', '--no-man-pages' , creating a distribution folder around 45mb.

If we want to use javapackager, for example to create an .DMG file, how can we do a similar compression? since these tags are not avaiable for javapackager. Without them the final bundle is around 100mb, losing a lot the java9 modularization advantages, so my question is if it is possible to use javapackager with JRE runtime images created by jlink.

thanks

I was able to use ZuluFX 8 with javapackager on Windows. However, on a Mac I get this error:

Bundler Mac Application Image skipped because of a configuration problem: Cannot determine which JRE/JDK exists in the specified runtime directory.
Advice to fix: Point the runtime directory to one of the JDK/JRE root, the Contents/Home directory of that root, or the Contents/Home/jre directory of the JDK.

It's pretty easy to just move the package into Contents/Home but I doubt that will work as it seems there is no JRE bundled with the Mac version of ZuluFX 8. Is this something that can be worked around?

• I built a small app using javafx ( very basic stuff )
• compile using javac : OK ( oracle jdk 1.8.0_201-b09 )
• crated the jar : OK : the jar works fine with java -jar

• packaged the app using javapackager

  javapackager \ -deploy \ -daemon \ -srcfiles $JAR_FILE:./lib/$LIB_JAR.jar \ -outdir $DIST_FOLDER \ -outfile dist \ -native deb \ -appclass com.myapp.client.gui.Main \ -name "MyApp" \ -title "MyApp" \ -v

• run the generated deb installer ( same machine )

• go the the installed app under /opt/MyApp, and when I ran MyApp it just complains about GLIBCXX_3.4.21 not found

I have tried all sort of apt fixes but nothing worked..

it's worth mentioning that this is all done in a fresh ubuntu desktop version running from a virtual machine. ( ubuntu 14.04.1 amd64 )

I'm trying to package a java application using java packager tool ( I'm new to this tool ) the app itself has to make some calls internally ( using the java process api )

This works fine if the java application is started with admin privileges. for example if I run my jar app as sudo java -jar application.jar from then all sub processes become admin as well.

For distribution purpose , I do not have control over how the users will start the app. thus trying to use java packager tool- but I need to enforce that the app is ran with admin privileges. ( fine the app will stop if the user does not have sudo for example )

The other workaround , which I strongly want to avoid is to ask the user to enter their admin/sudo password when I launch the internal processes..

---EDIT--- I think I needed to add more background after the comments and answer I got. as it looks to though the issue is about detecting admin or not.. this is not not what my issue is.

I develop and distribute a Java Swing app that uses Apache Batik and JavaCV. I've updated it through java 1.6, 7 and 8. Installers for macOS, Windows and Linux are built with Javapackager. Java 8 is end of support in Jan '19 and I can't find a solution to package and distribute at Java 11, the new LTS version.

Neither JavaCV or Batik produce modular jars but I have managed to repackage them to the point where I can compile and produce a runnable jar at Java 11, app works fine but I can't package it for distribution. I was planning dropping to Java 10 to use javapackager and bundle the 11 runtime from there but it uses jlink to produce a custom runtime, jlink fails because JavaCV and Batik aren't modular. jdeps won't produce a module-info.class to patch in and make them modular due to unsatisfied references in Batik and JavaCV, even though my app works fine without them.

As a result I'm going to have to leave the code base at Java 8, and ship it even though no longer supported.

I know there's a call to create a replacement for javapackager but that won't be there until way after Java 8 is deprecated. And I'd still need Batik and JavaCV projects to refactor and build modular jars to produce a custom runtime.

Can anyone offer any other solution please? Have I missed something? Thanks.

After long struggle I managed to generate (using Ant) on MacOSX (Yosemite) a DMG (of modular JavaFX application that deploys to *.app folder) even with custom icons of the app and DMG volume (both stored as *.icns files in build's package/macosx folder). Drag and drop works, it installs the app, the app launches so everything is fine. Well, almost.

I was tempted to make also the custom background for DMG. It is placed together with the icons in package/macosx folder as App-background.png file (where App part is the name of my app, as it is with icons). And javapackager actually picks up the background, but unfortunately after opening DMG the background seems to be placed in windows' top-left corner, the window itself is like twice the size of the background, so 3/4 of the window's background is just white.

I tried with different PNG sizes, but to no avail. DMG window is always way bigger than the image.

Is there any way to make javapackager (aka fx:deploy which I actually use) to generate DMG with proper settings, that just make the DMG window fit background size?

Edit: It seems like DMG window has actually the size of the PNG (the original background file), but for some reason the image, when displayed as background, is "slightly" scaled down.