Running RemoteSwingLibrary with standalone JAR fails on invalid javaagent in JAVA_TOOL_OPTIONS

[lindmik]

When starting a local Java application with a Windows batch script using RemoteSwingLibrary, the java.exe process never starts up.

Robot Framework log.html shows on DEBUG level that it sets the JAVA_TOOL_OPTIONS to something invalid.

Set JAVA_TOOL_OPTIONS='-javaagent:"C:\SUT\__pyclasspath__"=127.0.0.1:57586'

By looking at the code, it seems like __file__ is resolved as __pyclasspath__, which suggests that this is a Jython issue.

Overriding the JAVA_TOOL_OPTIONS in the application's batch script will allow Java to start up, but of course then RemoteSwingLibrary won't be able to connect to it.

[jussimalinen]

How do you add RemoteSwingLibrary jar to your path? Do you add it to PYTHONPATH, JYTHONPATH, or CLASSPATH?

And also, do you use environment variable or a commandline argument ---pythonpath?

[lindmik]

Just on the CLASSPATH, like this:

set BASEDIR=%~dp0
set SUTDIR=C:\SUT
set APPDATA=%USERPROFILE%\Application Data

set LIBDIR=%BASEDIR%lib
set OUTPUTDIR=%BASEDIR%output
set TESTDIR=%BASEDIR%tests

pushd %SUTDIR%
set CLASSPATH=%LIBDIR%/;lib/
call java -cp %CLASSPATH% org.robotframework.RobotFramework run --loglevel debug -d %OUTPUTDIR% %TESTDIR%
popd

LIBDIR has remoteswinglibrary-2.0.0.jar and robotframework-2.8.6.jar.
lib under SUTDIR has the application's JARs.

[jussimalinen]

Actually if you add remoteswinglibrary-2.0.0.jar to JYTHONPATH instead of CLASSPATH it works.

The logic for finding where the jar is doesnt work from CLASSPATH... It is a bug in RemoteSwingLibrary I think, but at least there is a workaround for now.

[ehhc]

See my comment here: #42