App failing to load when the .jar is downloaded from Github release

[Hikmet Emre Kaya]

Hello everyone,

I am not sure if anyone has encountered this before. I am developing an app for Cytoscape, and the .jar file works perfectly when I install it locally. 

However, if I download the same .jar file from my lab's GitHub page, where I uploaded it as a release, Cytoscape fails to load it.

It gets better: when I restart Cytoscape, the app in fact does get loaded and works just fine again.

Is there a step I am missing when releasing the file when on Github?

Thanks a lot!

Emre

[Alex Pico]

Hi Emre,

Please share the GitHub url to the jar so we can reproduce and (hopefully) diagnose the issue.

- Alex

> --
> You received this message because you are subscribed to the Google Groups "cytoscape-app-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to cytoscape-app-...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/cytoscape-app-dev/86e56ec0-9622-496b-bc00-4b1d4213d79en%40googlegroups.com.

[Hikmet Emre Kaya]

Hello Alex,

Thank you for the response. Here is the link: https://github.com/scientificomputing/CytoCopasi

One first needs to copy the native libraries to java.library.path for it to work properly - i.e., import files, run simulations etc., (I have been trying to automate this, but it is nearly impossible with the latest Java versions). But that's beside the point. If you just install the .jar file without the preliminary steps, the app should still load and appear in the left Cytoscape panel.

Let me know what you come up with. Could you also let me know what OS you test this in?

Best,

Emre

[Scooter Morris]

Greetings,

I just tried this on my Linux machine (Fedora 36, Java 17) and it loaded just fine.  I didn't do any of the preliminary steps, but the side panel definitely showed up.

-- scooter

[Hikmet Emre Kaya]

Hello Scooter,

I am glad to hear that! I actually found the issue, which was in my CyActivator, and fixed it. So it did load in my case as well. So it was not even related to GitHub after all.

Regards,

Emre