Chicken Wing Posted September 9, 2015 Share Posted September 9, 2015 (edited) Can anyone explain what this stacktrace actually means? [ERROR][09/09 05:21:38 PM]: Uncaught exception! java.lang.NoSuchMethodError: core.Node.<init>(Lcore/Fletcher;)V at nodes.cut.OpenBank.<init>(OpenBank.java:12) at core.Fletcher.onStart(Fletcher.java:85) at org.osbot.rs07.event.ScriptExecutor.onStart(ni:197) at org.osbot.rs07.event.ScriptExecutor.start(ni:46) at org.osbot.com2.run(dn:246) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) My script was working fine, and compiles fine, but now even if I make a new project in eclipse and copy over .java files which i know are fine and run the jar I get this error, even when I use the same .java files which are used in the script on the sdn (and the sdn script works). Edited September 9, 2015 by Chicken Wing Quote Link to comment Share on other sites More sharing options...
Alek Posted September 9, 2015 Share Posted September 9, 2015 Are you compiling against the most recent OSBot version? Are you sure you're using all packages correctly? Quote Link to comment Share on other sites More sharing options...
Bobrocket Posted September 9, 2015 Share Posted September 9, 2015 Show us your package structure. Quote Link to comment Share on other sites More sharing options...
Apaec Posted September 9, 2015 Share Posted September 9, 2015 Rename all your class files (or atleast the one being pointed to by this)... see if that changes anything. apa Quote Link to comment Share on other sites More sharing options...
Chicken Wing Posted September 9, 2015 Author Share Posted September 9, 2015 (edited) Are you compiling against the most recent OSBot version? Are you sure you're using all packages correctly? Show us your package structure. Im using version 2.3.110, Edited September 9, 2015 by Chicken Wing Quote Link to comment Share on other sites More sharing options...
Bobrocket Posted September 9, 2015 Share Posted September 9, 2015 Im using version 2.3.110, Refactor node to something like _Node, it's a problem because osbot thinks you're trying to initalise an OSBot node. You could also specify it's a core.Node rather than just a Node Quote Link to comment Share on other sites More sharing options...
Lemons Posted September 9, 2015 Share Posted September 9, 2015 Ever try "cleaning" your workspace? Aka deleting all the binaries and recompiling? Quote Link to comment Share on other sites More sharing options...
Chicken Wing Posted September 9, 2015 Author Share Posted September 9, 2015 (edited) Refactor node to something like _Node, it's a problem because osbot thinks you're trying to initalise an OSBot node. You could also specify it's a core.Node rather than just a Node Refactoring does nothing, as I said the script was working with the exact same code I have right now, I think its some sort of build path error Ever try "cleaning" your workspace? Aka deleting all the binaries and recompiling? Yes, I did that twice, I even deleted the whole project, made a new one and copied over .java files which were uploaded to the sdn EDIT: I FIXED IT, NVM GUYS Edited September 9, 2015 by Chicken Wing Quote Link to comment Share on other sites More sharing options...
