sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #36538
Re: [Question #281182]: Null pointer exception using Sikuli in Java
Question #281182 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/281182
RaiMan proposed the following answer:
Thanks for testing, but ...
--1. the log message:
.... runs as .... in: .... (produced by log(lvl, "runs as %s in: %s", jn, fSxBase.getAbsolutePath()); )
is missing in the log you gave me.
--2. in your test with a correct environment setup (only sikulixapi.jar
is on class path), clsRef should be null, since neither clsRef =
Class.forName("org.sikuli.ide.SikuliIDE"); nor clsRef =
Class.forName("org.sikuli.setup.RunSetup"); should work.
I see 2 aspects:
- purge SIKULI_HOME from your environment (SikuliX 1.1.0+ does not need nor use that any more). So if you accidentally have other references to "wrong" Sikuli stuff, then you should get other errors.
- take care, that neither sikulix.jar nor the sikulixsetup...jar is on class path at runtime.
Take care that you are using the final 1.1.0, otherwise I cannot help
you.
You are saying, you are running a Maven project: Is sikulixapi.jar
referenced so that it is taken from MavenCentral?
--
You received this question notification because your team Sikuli Drivers
is an answer contact for Sikuli.