Running compiled Jython scripts packed in a jar with option -r (related #392)

[RaiMan]

This post is only to document the status.
How we deal with it further, has to be evaluated and decided.

Motivated by the discussion #392, I had a look into this stuff:

• SikuliX IDE had a feature in the file menu, to pack compiled Jython scripts into jars
• these jars could be run from commandline using java -jar …ide…jar -r script.jar
• the code to build and run is available in Oculix, but is deactivated and not documented
• this seems to work: if you have a jar built with SikuliX, you can run it with Oculix with the -r option

I had a look through the build code and did some minor fixes, so the build of such jars now works in Oculix.

To test it, I used this Jython script (easier than to make it in Java):

import org.sikuli.support.FileManager as FM
FM.makeScriptjar(("plain","/Users/raimundhocke/Downloads/GitProjects/Test/makejartest.sikuli", ))

The script to pack (makejartest.py) simply a one liner:
print "hello from makejartest“

The minor fixes are in claude/i18n-phase3 commit b31b0ae

There is also a version in the code, that packs a Java main() into the jar, together with support to populate the classpath at runtime with the needed jars to run it.
I suggest to not make this available as a feature, since it is more complex, without having any advantages.

[julienmerconsulting]

@RaiMan — thanks for the quick groundwork. Reading b31b0ae and tracing through FileManager.doMakeScriptjar, I noticed the embedded prolog still pointed at an old class path that no longer exists in OculiX. I folded the correction into the rebase and added the IDE surface so the feature is discoverable for users like @cipriantrofin (#392).

🧩 What's now on claude/i18n-phase3

Commit	File	Change	Why
b31b0ae	Commons.java, JythonSupport.java, FileManager.java	Reflection path refactor, defensive list copy, prolog migration	Revive makeScriptjar and the -r flow
706b9be	FileManager.java l. 940	org.sikuli.suport.SikulixForJython → org.sikuli.support.SikulixForJython	One-character p on the migrated path. The original org.sikuli.script.SikulixForJython was already stale (the class has been at org.sikuli.support since the modules split), so the generated jar would have ImportErrord on first run either way.
54fdd08	SikulixIDE.java	File ▸ Export becomes a sub-menu: As .zip (workspace) · As .jar (script library) · As runnable .jar	The two jar items were dormant since the menu cleanup pass — doAsJar / doAsRunJar were intact but no menu entry was wired to them
cbe8cb6	22 × IDE_*.properties	Drop menuFileExport= key	Sub-menu siblings are EN-inline ("Export" is universally understood); keeps the bundles in sync with the new JMenu definition

🧪 Validation requested

I haven't run a fresh build + jar export end-to-end yet. If you have a minute on Mac, the same Jython snippet you used to test in b31b0ae should now produce a runnable jar without the import error. @adriancostin6 — if the Linux box is up, mirroring your cross-OS pass from #348 would close the loop here.

🦎

[RaiMan]

@julienmerconsulting
Happy to have you at the side of the courtyard: Thought I fixed the double p problem - but apparently not - sorry and thanks.

As mentioned: I do not think, that the as runnable .jar makes sense. And in fact it would not work, since needed main class SikulixRun is no longer available. On the other hand it has no advantages, since in any case you would need the ide jar to run the stuff. So IMHO doAsJar is sufficient.

Will come back after having a look at it.

[RaiMan]

@julienmerconsulting
On compile I get these errors in the MCP section:

ReadTextInRegionTool.java
Symbol nicht gefunden :25
Methode überschreibt oder implementiert keine Methode aus einem Supertyp :27
Methode überschreibt oder implementiert keine Methode aus einem Supertyp :28
Methode überschreibt oder implementiert keine Methode aus einem Supertyp :32
Symbol nicht gefunden :36
Methode überschreibt oder implementiert keine Methode aus einem Supertyp :40
Symbol nicht gefunden :41
Symbol nicht gefunden :54

and also in FindTextTool.java, ToolRegistry.java (many Symbol nicht gefunden )

Please help.

[RaiMan]

@julienmerconsulting
Excluded MCP from the Maven build and tested: works