You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 4, 2023. It is now read-only.
Once I copied the JDK into the Frameworks folder, everything just works now. It wasn't there before and so the universalJavaApplicationStub began to look for Java on my system and I guess it found ":/bin/java" somehow.
Now that I formatted your initial post with proper codeblocks I see the problem. Sorry for not having seen this in the first place.
I added some more debug logging for this case with commit 0880026
20:26:15.320409+0100 [5775][App] [JavaSearch] Checking for $JAVA_HOME ...
20:26:15.331929+0100 [5775][App] [JavaSearch] ... found JAVA_HOME with value Contents/Resources/Frameworks/amazon-corretto-8.jdk/Contents/Home
20:26:15.339730+0100 [5775][App] [JavaSearch] ... parsing JAVA_HOME as relative path inside the App bundle to the executable '/Users/xxxxx/dev/universalJavaApplicationStub/test/test.app/Contents/Resources/Frameworks/amazon-corretto-8.jdk/Contents/Home/bin/java'
20:26:15.361691+0100 [5775][App] [JavaSearch] ... but no 'java' executable was found at the JAVA_HOME location!
The found JVM: :/bin/java resulted from another issue (#93) where /usr/libexec/java_home/ did not return any registered JDKs. This has been fixed in the meantime.
I'm submitting a…
Short description of the issue/suggestion:
This is the Java output when running commands from terminal:
This is the console log:
I'm using universalJavaApplicationStub 3.1.0.
Steps to reproduce the issue/enhancement:
What is the expected behavior?
What is the current behavior?
Do you have screenshots, GIFs, demos or samples which demonstrate the problem or enhancement?
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Other information (e.g. related issues, suggestions how to fix, links for us to have context)
The text was updated successfully, but these errors were encountered: