#212 Executable doesn't run with bundled jre if in a folder containing spaces (jni or not)

[JPDelprat]

Generated executable doesn't run with a bundled jre if in a folder containing spaces (jni mode or standard mode).
Both the executable and the bundled jre are under the folder containing spaces.

I got the following message :

java.lang.NoClassDefFoundError: com/a/launcher/Launcher
Caused by: java.lang.ClassNotFoundException: com.a.launcher.Launcher
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
Exception in thread "main"

[Grzegorz Kowal]

I will try to fix this.

Best regards,
Grzegorz

On Tue, Mar 9, 2021, 23:47 Jean-Pierre Delprat jeepy31@users.sourceforge.net wrote:

---

• [bugs:#212] https://sourceforge.net/p/launch4j/bugs/212/ Executable
  doesn't run with bundled jre if in a folder containing spaces (jni or not)*

Status: open
Group: 3.x
Created: Tue Mar 09, 2021 10:47 PM UTC by Jean-Pierre Delprat
Last Updated: Tue Mar 09, 2021 10:47 PM UTC
Owner: nobody

Generated executable doesn't run with a bundled jre if in a folder
containing spaces (jni mode or standard mode).
Both the executable and the bundled jre are under the folder containing
spaces.

I got the following message :

java.lang.NoClassDefFoundError: com/a/launcher/Launcher
Caused by: java.lang.ClassNotFoundException: com.a.launcher.Launcher
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
Exception in thread "main"

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/launch4j/bugs/212/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[JPDelprat]

Thanks a lot.
I thinks it would be interesting an interesting fix, because it allows to start the executable from "C:\Program Files"' for instance.

However, in my case, I've found another solution so it's not urgent any more for me.

Best regards,
Jean-Pierre

[Loic Decloedt]

Hi all,
I indeed experienced the same problem. I tested this case on purpose as this was something we already saw in the past.
I am happy this has already been detected. This is a mandatory feature to adopt Launch4J. By doing internal investigations we found a stackoverflow page that explains the root cause on windows and how it can be solved:
https://stackoverflow.com/questions/53218984/how-can-i-avoid-the-windows-exec-and-spawn-functions-splitting-arguments-at/53220680#53220680

Cheers,
Loïc.