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
On Mac OSX (10.9), ohab2 startup stalls while installing script engines. The reason is that a 'AppleScript' script engine is present, which later blocks the class loader while attempting to load that engine.
(I realize this should probably go to the ESH side of things, just don't think that patch is up to snuff for them :), perhaps someone around here has a better fix)
The text was updated successfully, but these errors were encountered:
@HentschelT, I realize this has been aroud for a long time, but I'm trying to get some of the automation issues cleaned up. Have you tested your proposed fix, and did it correct the problem? I would implement it, but all it is doing is preventing the logger.debug line from running, so I don't see how it could resolve the issue. Also, which version of the JDK were you using?
AppleScript was removed from JDK 10(search for AppleScript), so this is something that will not be an issue for much longer. That document also states...
The AppleScript engine has been mostly unusable in recent releases. The functionality worked only in JDK 7 or JDK 8 on systems that already had Apple's version of the AppleScriptEngine.jar file on the system.
If I'm understanding this, it sounds like this issue would only be a problem for people that had previously installed the AppleScriptEngine.jar. I assume this can also be uninstalled to correct the issue.
On Mac OSX (10.9), ohab2 startup stalls while installing script engines. The reason is that a 'AppleScript' script engine is present, which later blocks the class loader while attempting to load that engine.
Attached is a patch, which -- in a hacky way -- bypasses loading that engine. IWFM, I don't need AppleScript.
ESH-automation.module.script.patch.txt
(I realize this should probably go to the ESH side of things, just don't think that patch is up to snuff for them :), perhaps someone around here has a better fix)
The text was updated successfully, but these errors were encountered: