Question #234120 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/234120
Status: Open => Answered RaiMan proposed the following answer: As mentioned with the release information: do not put the new stuff into an existing Sikuli installation folder ;-) If you want to stick with your current folder setup, just copy the old stuff into a safe place, to restore it if necessary. Then empty the target installation folder, download sikuli-setup.jar into it and run the setup. Beginning with 1.0.1 only the one jar and eventually the corresponding command script is of relevance for saving/restoring (the libs folder is always checked and restored if necessary from the jar) - so just forget the libs folder. In your case: if you want to move stuff around for whatever reason (though you should know, what you are doing ;-), these are the 2 files: sikuli-script.jar runScript.cmd If you are using import of Sikuli scripts in your scripts, you should wait a few hours: I have just fixed bug 1212763 -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. _______________________________________________ Mailing list: https://launchpad.net/~sikuli-driver Post to : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp