@edvin thank you, you really don't have to but I appreciate it.

@edvin been trying to follow instructions on command prompt

@User uploaded a file:

@thomasnield I should have given you the correct command, that would have been a lot easier.

@thomasnield

java -jar fxlauncher.jar --uri=file:///path/to/app

The path can probably also be relative.

@thomasnield To get a real test, you should have fxlauncher.jar in another folder. The next step would be to build a native installer with the file path.

@edvin okay awesome, let me try this. I was wondering if something was off...

@User uploaded a file:

@User uploaded a file:

What is the

--uri=file:///path/to/app

specifically? The project?

Alright made some progress. It needs to be formatted like

C:/path/to/my/folder

for Windows. But it's not finding the

App.xml

which I'm not sure how to generate without using Gradle.

This is only for Maven, isn't it? Don't we need to make a test version for the Gradle plugin too?

@thomasnield The uri should point to the folder where you have deployed your application. That means that the folder should contain app.xml as well as all the libraries for your app. Since you won't be using the

deployApp

gradle goal, just run

gradle embedApplicationManifest

to generate those files.

The 'embedApplicationManifest` ensure that these two other goals run first:

copyAppDependencies: Assembles the application into build/fxlauncher generateApplicationManifest: Generates app.xml into build/fxlauncher embedApplicationManifest: Copies app.xml into fxlauncher.jar

So you'll find your app in build/fxlauncher. Put this in a folder, and that is the folder you should reference in the uri parameter.

Now you won't need to specify that uri parameter anymore, you can actually just copy out fxlauncher.jar to an empty folder and run it with java -jar fxlauncher.jar, and it should use the uri embedded into it (provided that you configured the 'applicationUrl` to point to that folder.

You just need to copy the files from builder/fxlauncher to the folder you specified in applicationUrl, and distribute either the native installer or just fxlauncher.jar. So to test it, first copy fxlauncher.jar to another folder and run it.

When tar works, you can create a native installer, try to install it and run the resulting program.

Whoa, I think that worked. For some reason Intellij IDEA Gradle was causing a lot of issues

But command line worked fine

Copying over right now...

Never mind! It works. Just had two coworkers run it without issue, who only have Java 6 : D

@edvin thanks a lot, I do not take your amazing work for granted. This is awesome!

@thomasnield Cool! So you even ran it with the installer?

@thomasnield Happy to hear that. You probably want more customizations to this as you play more with it.

I'll release FXLauncher 1.0.17 tomorrow 🙂

@edvin

List<LibraryFile> needsUpdate = manifest.files.stream() ...

why are you using java's streams? Just curious

Wait this is written in Java haha