Details
-
Type:
Bug
-
Status: In Progress
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 2.11.2
-
Fix Version/s: None
-
Component/s: gui
-
Labels:None
Description
As noted in comment https://issues.jalview.org/browse/JAL-3728?focusedCommentId=25322&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-25322
The running Jalview icon in the macOS Dock has the name "java", although its icon is correct.
There does not appear to be a way to change this either programmatically or command line arguments (the "-Xdock:name=Jalview" argument no longer works since [apparently] around macOS 10.9).
The appearance of "java" is because Getdown launches the java executable as a separate process in order to allow memory settings to take affect.
Three possible solutions I can think of, two of which would be quite a major task/change though could be in a long term plan.
1) Use Java 11+ modules and jlink to compile macOS Jalview as its own "native" executable with Info.plist.
2) Create and compile a JNI launcher (not dissimilar to the install4j launcher) for getdown to run instead of the java executable.
3) This appears to work: make a symbolic link to the jre/bin/java executable called "Jalview" (or "Jalview Develop") and have Getdown (and jalview.bin.Launcher?) check for the existence of that, that it's pointing to "jre/bin/java" and call that instead of "jre/bin/java".
I think 3, whilst being a bit hacky, gives the best return for time taken!
The running Jalview icon in the macOS Dock has the name "java", although its icon is correct.
There does not appear to be a way to change this either programmatically or command line arguments (the "-Xdock:name=Jalview" argument no longer works since [apparently] around macOS 10.9).
The appearance of "java" is because Getdown launches the java executable as a separate process in order to allow memory settings to take affect.
Three possible solutions I can think of, two of which would be quite a major task/change though could be in a long term plan.
1) Use Java 11+ modules and jlink to compile macOS Jalview as its own "native" executable with Info.plist.
2) Create and compile a JNI launcher (not dissimilar to the install4j launcher) for getdown to run instead of the java executable.
3) This appears to work: make a symbolic link to the jre/bin/java executable called "Jalview" (or "Jalview Develop") and have Getdown (and jalview.bin.Launcher?) check for the existence of that, that it's pointing to "jre/bin/java" and call that instead of "jre/bin/java".
I think 3, whilst being a bit hacky, gives the best return for time taken!