sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #27058
[Question #251689]: Java Sikuli program works within Netbeans but fails once built as a Jar
New question #251689 on Sikuli:
https://answers.launchpad.net/sikuli/+question/251689
Hello all,
I have a Java project which processes automation against an insurance system using the Sikuli library. I've set my project up as follows:
• Imported sikuli-ide.jar into the Libraries folder (added to the "Compile" tab within the "Libraries" section of project properties).
• imported the relevant Sikuli functionality within my class hierarchy as needed e.g. "import org.sikuli.script.Screen;".
• App works fine when running from within Netbeans. Attempting to run the finished Jar from the Dist folder I first receive the following errors:
[error] ResourceLoaderBasic: check: No valid libs path available until now!
[action] ResourceLoaderBasic: check: Please wait! Trying to extract libs to jar parent folder: F:/NetBeansProjects/I90AutomationTool/dist/lib/
After a short pause the script appears to start but none of the keystrokes actually function.
Here is a screenshot of the app working when being run from Netbeans: http://i59.tinypic.com/316qgw8.png
When I run the final Jar from the Dist folder the "Keystroke" text field is populated with the above warnings.
I suspect that when the sikuli-IDE is moved to the Dist folder the file path is changing in such a way that the app is not able to import the classes any longer (a bit like if you've ever had to reference images within a Jar using getResource()). Just a hunch.
Any ideas?
Thanks,
Nathan
--
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.