SOFA 2.0 Editor - GUI Repository Designer for Eclipse



SOFA 2.0 repository editor v. 1.3.0 released. Changes »


SOFA 2.0 repository editor v. 1.0.149 released.


Work on the plug-in is started. History »


Compiling and installation

User's manual

Usage scenarios

Developer's manual

UML diagrams

Java docs

Author MaViNes (c)


OSGI Framework

Eclipse plugin basics

RCP basics

SWT draw basics

jFace tips

SWT Linux/Windows differences

Author MaViNes (c)

Install plug-in from source codes

To install the plug-in from the source code distribution you need to download the zipped file which contains source codes for the plug-in itself, the plug-in's feature, and the plug-in's deployment site. The bundle is located here.
Unzip the file to a folder and open Eclipse IDE. When eclipse is open, you shoud mouse right-click in the files explorer, choose Import... and use Import Wisard to import existing project into workspace. You should import all 3 projects into the Eclipse workspace. Please make sure you have 3 new folders in the file explorer - plugin.core,, plugin.features. After you have all these projects imported, you can compile the plugin.core to the deployment state. This meens you should open the project plugin.core, then open the file plugin.xml in the root of the project and at the first tab of the plugin.xml editor you should click on the 'Export' link. This will open the Export wisard. There you should choose the project to be exported to the folder, and the exported plugin should be packed as jar archive. When the project is succesfullty exported, you can close the plugin.core project and open the plugin.feature project. In the root of this project you should open the feature.xml file and in the feature.xml editor click on the 'export' link. This will open the Export wisard, in which you have to set export folder to the project location and choose newly exported feature to be packed as a jar archive. Then click export.
After all of this is done, you are nearly to have predeployed plug-in. The last step you should do is to close plugin.feature project and open project. In the project you should open the site.xml file and in the site.xml editor firstly click on the 'Synchronize' button and choose synchronize all, then perform synchronization. And after the synchronization is done, you should click on the Build button and choose build all option. then perform build. Now the plug-in is ready to installation. Please close all projects and open the Help->sofatware updates->fina and install wizard. In this wizard click on the 'new local site' button and set the folder to the project location. Set the name: 'SOFA 2.0 repository editor'. Then click the Finish button and perform the plug-in installation as described in the 'binary installation' section of the documentation.

NOTES: 1. Plug-in version. The plug-in version can be changed in the plugin.xml editor on the Overview tab. After the version is changed, the according changes should be performed in the plugin.feature project and the project. In the plugin.features project the version should be forsed to be copied from the plugin.core project version. This can be done at the Plug-ins tab of the feature.xml editor. Please make sure both versions (in the plugin.core project and in the plugin.features project) are equal. Then save the plugin.features project and go to the project. Here open the site.xml editor and remove actual feature from the list of properties. This should be done because the version is changed and site.xml can not see newly created feature and plug-in. After the old feature is removed, add the new one to the same place. The only difference now is version number. Then synchonize and build all features from the site.xml editor.

Build plug-in from the ant script

Pre-requisites: To build the plugin from the ant build.xml file you should download the file with zipped sources of the plugin.core, plugin.features, xml and unzip the file to a folder. Than change dir to the folder and perform 'ant build.update.jar'. This should build a jar file with needed plug-in inside.
But the plugin.features and projects you have to deploy using the export wizard from Eclipse. Those project do not contain any java source files and there is no build.xml predefined for those projects. The site.xml file can be edited manually bacause it has very simple structure. Just name of a deployed feature and attributw whether it is patch for onther feature or not.
The feature.xml file should be packed to a jar file with the same name as the plug-in's jar file, but should be stored in the features folder of the project. The syntax of the feature.xml file is a bit more complex that the one of the site.xml, but it still can be edited manually, and for now it is not required to edit it much. Just in case the plug-in's version is changed.