-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Status of Version 0.8.0-beta2 tried on macOS Monterey (12.6.6) #87
Comments
I have a few Java versions installed on my MacOS Ventura and tried versions 8, 11 and 17 - all they work as well. |
Hello,
Am 27.09.2023 um 16:18 schrieb Vladyslav ***@***.***>:
I have a few Java versions installed on my MacOS Ventura and tried versions 8, 11 and 17 - all they work as well.
Just stating "works for me" with just few additional details does not help too much. ;-)
Are we talking about Oracle java, or free versions, such as OpenJDK? What is the output of your java --version?
Also, what about the missing execute flag?
:wq! PoC
|
Where have you downloaded your Version? How/where exactly do you get the error message? Could you provide a screenshot? Have you tried to start the tn5250j.jar from Terminal with |
Maybe duplicate issue |
Am 27.09.2023 um 17:06 schrieb Sascha ***@***.***>:
Where have you downloaded your Version?
On the project's main page https://github.com/tn5250j/tn5250j in the "Releases" section.
How/where exactly do you get the error message?
After unpacking tn5250j-0.8.0-beta2.osx-app.zip, I double-click the resulting application icon and get the error message from the Finder "The application 'Tn5250j' cannot be opened". I translated this from German, because I'm using a German OS. I can only click "OK".
Could you provide a screenshot?
Not sure if this is helpful due to German language. Will do, to.
Have you tried to start the tn5250j.jar from Terminal with java -jar tn5250.jar?
I'm sorry to not have mentioned that right from the start. Yes, this works. Although I'm getting these warnings:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.tn5250j.gui.AppleApplicationTools (file:/Users/poc/Desktop/Tn5250j.app/Contents/Resources/Java/tn5250j.jar) to method com.apple.eawt.Application.getApplication()
WARNING: Please consider reporting this to the maintainers of org.tn5250j.gui.AppleApplicationTools
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
How does your JAVA_HOME environment variable look like?
For an ordinary shell, there is none. I don't know nothing about Java. To me it seems to be a necessary nuisance. ;-)
Again, Cisco ASDM and IBM iAccess work fine.
:wq! PoC
|
Am 27.09.2023 um 17:08 schrieb Sascha ***@***.***>:
Maybe duplicate issue
#82
Huh! I did not see that, sorry!
I can confirm that the solution shown by jamespullman works for both versions 0.8 and 0.7.6.
:wq! PoC
|
Apparently, attachments on mails aren't handled by GitHub. Sorry! Anyway, as said, the solution in #82 works for me, too. I'm running on Intel and observed the described problems with macOS 11 and 12. So the heading of #82 might be misleading. Thanks! |
When trying to run 0.8.0-beta2 for MacOS X on macOS Monterey (12.6.6), I get the error message "The Application 'Tn5250j' cannot be opened."
Having a closer look, it appears that just the execute-flags are missing from
Tn5250j.app/Contents/MacOS/universalJavaApplicationStub
. Fixing withchmod +x
brings up the familiar dialog about unsigned applications.That can be fixed by right-clicking and choosing "open" in the contextual popup menu. Now, I get the error that no suitable Java version wasn't found on my system.
I have updated just now to the latest OpenJDK11U-jdk_x64_mac_hotspot_11.0.19_7.pkg:
I have a local install of Cisco ASDM, and IBM iACS, both running just fine with the installed and updated Java. Not sure what I can do from here?
Note: The same eventual error (no suitable Java) happens with 0.7.6.
The text was updated successfully, but these errors were encountered: