coArchi 0.8.0 CLI plugin not loading with Archi 4.9.0 on Linux

Started by davidMbrooke, October 21, 2021, 14:51:45 PM

Previous topic - Next topic

davidMbrooke

I'm seeing an issue with Archi 4.9.0 and coArchi 0.8.0 when using the Archi Command Line mode to read a Model and generate an HTML Report (Linux variant of Archi on Ubuntu 20.04.3).

I'm following the exact same procedure as for Archi 4.8.1 with coArchi 0.7.1 and that works perfectly.

The underlying problem seems to be that the coArchi plugin isn't loading, despite me unzipping the .archiplugin file in the /opt/Archi/plugins/ directory, such that I see the org.archicontribs.modelrepository files alongside all the other .jar files in that directory:
...
org.apache.lucene.core_8.4.1.v20200122-1459.jar
org.apache.xmlgraphics_2.6.0.v20210409-0748.jar
org.archicontribs.modelrepository.commandline_0.8.0.202110121448.jar
org.archicontribs.modelrepository_0.8.0.202110121448.jar
org.bouncycastle.bcpg_1.69.0.v20210713-1924.jar
org.bouncycastle.bcprov_1.69.0.v20210713-1924.jar
...
The file permissions look OK and when I inspect the contents of the .jar files with 'unzip' the contents closely match the same files for coArchi 0.7.1.

When I specify the --help argument, I'm not seeing " [Load & Clone Collaboration Model] " under "Registered providers:" (running 4.9.0) - which presumably explains why  --modelrepository.loadModel  does nothing.

Is there anything different / extra I need to do when installing the coArchi plugin on Linux with Archi 4.9.0?

Phil Beauvoir

October 21, 2021, 14:55:06 PM #1 Last Edit: October 21, 2021, 15:15:46 PM by Phil Beauvoir
What do you see when you select Help -> Manage Plug-ins...

Also, don't put the jars in the root "plugins" directory. Create a root "dropins" directory and put them there or install via the Plugins Manager.
If you value and use Archi please consider making a donation! https://www.archimatetool.com/donate

davidMbrooke

Thanks Phil.

I'm running the report generation "headless" via Docker so there's no easy way to inspect via a GUI.

Installing on a different Linux machine, with a screen, and using Help > Manage Plug-ins I can see it loads the Plug-in .jar files into $HOME/.archi4/dropins/

Now I've unzipped the .archiplugin file in that same location on my "headless" machine it's working fine.

All good; thanks again.