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
CoffeeScript support does not work #92
Comments
Simple integration of CoffeeScript support. The code uses the JavaScript implementation of the CoffeeScript compiler. All *.coffee files get compiled to JavaScript just before eval(). Additionaly a new command named /coffe is introduced to run CoffeeScript code straight in the Minecraft console.
Works good on my side. What Java RE do you have installed?
I found this one: http://coachwei.sys-con.com/node/676073/mobile I'll try to reproduce the problem with the Oracle JRE. |
java version "1.6.0_27" |
Hi @aaronmueller , |
No, I've had some problems running multiple Java versions on my machine and hadn't time to investigate the problem here. But I've done some research. The main problem seems this:
Java6 tries to compile the coffeescript.js file to Java bytecode and failed. To prevent this, the According to the documentation, we need to call Can you please try this? |
Hi Aaron, ScriptCraft uses the javax.script package bundled with Java 6/7. It no longer uses or depends on Rhino. |
I'm getting errors when the Java plugin attempts to load and evaluate the _coffeescript.js file (it's there - I've downloaded it) ...
21:53:56 [SEVERE] javax.script.ScriptException: sun.org.mozilla.javascript.EvaluatorException: Encountered code generation error while compiling function "null": generated bytecode for method exceeds 64K limit. (#8) in at line number 8
21:53:56 [SEVERE] at com.sun.script.javascript.RhinoScriptEngine.eval(RhinoScriptEngine.java:183)
21:53:56 [SEVERE] at javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:249)
21:53:56 [SEVERE] at net.walterhiggins.scriptcraft.ScriptCraftPlugin.onEnable(Unknown Source)
See 7205646
The text was updated successfully, but these errors were encountered: