I've been attempting to create a packaged version of Archi 4.9.1 following the instructions here - https://github.com/archimatetool/archi/wiki/How-to-create-a-packaged-version-of-Archi-(including-configuration-and-plugins)#add-plugins - and it mostly works, except I can't seem to get it to recognise plugins provided - specifically coArchi & JArchi.
I've followed the instructions and dropped the .jar files for the plugins into the plugins folder, (and a few different variations to this too) but they are never recognised when Archi starts.
I saw something where you had some issues around plugins and Eclipse a while back so I was wondering if there is something else I need to be doing? Any ideas?
it won't work if you put additional plug-ins in the "plugins" folder. They must go in a folder named "dropins" at the same level:
---dropins <- Here
Aha, thanks Phil, that's what I was missing :). I see you've updated the wiki page too, thanks heaps.
An update to this.
Copying the *.jar files into the "plugins" folder used to work. That is until I broke it. Will be fixed in the next version of Archi.
Having said that, it is still better to put them in the "dropins" folder so they show up in the Plugins Manager.
QuoteHaving said that, it is still better to put them in the "dropins" folder so they show up in the Plugins Manager.
I'm not able to test at the moment so I have a question: do you mean that we can have both a user "dropins" folder and a main "dropins" folder in the Archi installation directory at the same time?
If yes, I agree that's the best way to do it, if no, being able to ship custom plugins into the main "plugins" folder is needed (at least I rely on it for our "corporate" Archi distribution in which I ship coArchi & jArchi by default.
Yes, in fact three possible locations. See the code comments at https://github.com/archimatetool/archi/blob/master/com.archimatetool.editor/src/com/archimatetool/editor/p2/DropinsPluginHandler.java
Being able to put them in the "plugins" folder was a side effect of the "artifacts.xml" being present in the root folder. For Archi 4.9 I removed that in the binaries because I thought it was not used for anything. Seems it has some meaning for Eclipse.
But the "plugins" folder is not a good place to put them for the Plugins Manager because it doesn't list them in the dialog. If it did it would list all plugins and we don't want that.
One more question related to this, but on a slightly different topic, for scripting, I'd like to include a set of scripts in the build.
There was a post a while back where Phil talked about putting them in the folder defined by the preferences in Archi, which is fine after the fact, but if I want them to be picked up by the extraction of the build (or I guess more precisely, when Archi starts and it creates the folder where config etc are created for the first time), where do I put those scripts in the build to make that happen?
Quote from: mjtapp on November 10, 2021, 04:52:27 AMbut if I want them to be picked up by the extraction of the build (or I guess more precisely, when Archi starts and it creates the folder where config etc are created for the first time), where do I put those scripts in the build to make that happen?
I'd to be able to do it too, but for the moment you can't do it.
Aha, thanks JB, I had a feeling you were going to say that :). No problem, I'll just to work around it.