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
It seems there is a long-standing problem with the Java launcher and non-ASCII paths on Windows. See this open Java bug: https://bugs.openjdk.org/browse/JDK-8124977 The result is that with BlueJ, if you double-click a package.bluej file in a directory with non-ASCII characters, it can fail to load, usually with a message about being unable to extract the archive.
This answer on Stack Overflow suggests a work-around involving JNA but it's quite hacky as it involves picking through the raw command line to deduce which bits are the actual arguments: https://stackoverflow.com/a/70573213
The text was updated successfully, but these errors were encountered:
It seems there is a long-standing problem with the Java launcher and non-ASCII paths on Windows. See this open Java bug: https://bugs.openjdk.org/browse/JDK-8124977 The result is that with BlueJ, if you double-click a package.bluej file in a directory with non-ASCII characters, it can fail to load, usually with a message about being unable to extract the archive.
This answer on Stack Overflow suggests a work-around involving JNA but it's quite hacky as it involves picking through the raw command line to deduce which bits are the actual arguments: https://stackoverflow.com/a/70573213
The text was updated successfully, but these errors were encountered: