|Re: How to build a Sirius product without using update mode? [message #1848237 is a reply to message #1848183]
||Thu, 25 November 2021 18:35
|| Steve Monnier
Registered: May 2011
The plugin-based approach to deploy your plugins in a new Eclipse installation would be by selecting your plugins, then choosing the contextual menu "Export", then select "Plug-in development > Deployable plug-ins and fragment". This will lead you to a window where you can select all the plugins you want to export (if you selected the ones you need, they will be already selected here). At the bottom of the window, you can select a directory where you will have each plugins exported as a .jar file or you can choose archive file that will produce an archive containing each project as a jar.
To deploy these plugins in a new Eclipse environment, you can just copy/paste the .jar files in the "plugins" folder of this new Eclipse or you can copy/paste the archive in the dropins folder (You may be able to drop the .jars in the dropins folder but I do not remember if that works). When you launch this new Eclipse, it will load your new plugins as well and be ready to work.
As you see, it is a quicker way to deploy. It is not really "updatable", but you can still replace an old version of the exported jar and restart (you may need to add the "-clean" option to the eclipse.ini to reload plugins). It is a quick way to test, but I would not recommand to deploy your Sirius product that way, as it would look like your solution is "cobbled together" (I am not sure if it is the proper expression here) compare to a feature-based approach where you can also quickly produce an update site. You can also produce your own bundle with Tycho, but that is a whole other level of product building.
Steve Monnier - Obeo Canada
Need training or professional services for Sirius?
Powered by FUDForum
. Page generated in 0.01856 seconds