Unknown command ' -jar'. about update4j

[mordechaim]

Everything after the -m command is passed as application arguments. Meaning the -jar flag had zero effect on the JVM. The reason it worked before was that unknown commands were silently ignored by the DefaultBootstrap. In 1.3.0 this changed. The -jar and -m commands are mutually exclusive. The first always wins, so -jar first starts in the classpath and -m first starts in the modulepath. The error you receive about no providers, i don't really know why it's happening, does it happen if you use just -jar without -p? I'm going to test it myself later.

[painos]

Yes, same result with only -jar.

[mordechaim]

Did you build from source or used the Maven artifact?

[painos]

Maven artifact

[mordechaim]

Please post your environment details, as JVM version and operating system.

[painos]

Windows 7 Enterprise
java version "10.0.2" 2018-07-17
Java(TM) SE Runtime Environment 18.3 (build 10.0.2+13)
Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.2+13, mixed mode)

[mordechaim]

Could not reproduce the no providers found exception. 😢

Can you confirm you cannot run the demo application?

[painos]

No problem running with:
modulepath with -p modulepath/ -m org.update4j.

Only if trying with mixing -jar and modulepath:
java -p modulepath/ -jar update4j1.3.3.jar

Reason why I was trying this was I wanted to use launch4j which does not support launching only modulepath for now.

I think i will just settle using .lnk shortcut to javaw.exe and passing args to it for launching update4j in delegate mode and

[mordechaim]

I don't have an issue even with mixed paths.

Does it fail even outside launch4j, in the command line?

[painos]

I'm quite sure I was testing it in command line and getting the fail, but now I try again and it works.
I'm sorry I wasted your time and thank you so much for helping.

Now I will take a deeper look at the demo app, so excited! :)