Setting Up Eclipse for SVN Plugin Development
Overview
The OpenArbor plugins have now been moved from CVS to SVN. This means that if you are doing plugin development, you will need to setup your Eclipse environment to point to and use the SVN repository. Please don't use CVS any more! Any changes to the CVS repository from this day forward will not be included in the OpenArbor or plugin builds.
So you ask yourself... how do I accomplish that? Well, below are some easy steps to follow.
Setting Up Eclipse for SVN Plugin Development
1) Install the command line version of SVN (you need this to run a script to create your new plugin workspace). Copy the .msi file to your temp directory and then double-click it to install it. Take all the default options...
\\Samba\projects\openarbor\Downloads\Subversion\Slik-Subversion-1.6.3-win32.msi
2) Install the Subclipse plugins into your development Eclipse (or OpenArbor) installation
\\Samba\projects\openarbor\Downloads\Subversion\site-1.6.2.1.zip
Unizip the above zip file to your Eclipse development directory ie. C:\Eclipse3.4.0\eclipse <--- if you use Eclipse as your dev env... ie. C:\DDC-I_Build94\openArbor_v3.4.0 <--- if you use a version of OpenArbor as your dev env.... Fix path as needed.
3) Create a brand new empty workspace directory to hold the plugins....
ie. C:\ddci_eclipse\ddci-<fml>-workspace (where <fml> is replaced with your first, middle and last initial)
4) Copy the \\Samba\projects\openarbor\Downloads\Subversion\eclipse-workspace-checkout.bat file to the empty workspace directory you created in step 3.
5) Open a cmd window and cd to the directory created in step 3 and run the bat script.
6) Start Eclipse. File | Import | General | Existing Projects into Workspace. Select the workspace root for "Select root directory". All the checked out projects will be listed. Just press Next.
Note: The workspace will rebuild. If the "installer" projects contain errors. Close them. (You need to install RCP developer plugins into your Eclipse dev env if you want to make the plugin and OpenArbor installer .exe for these errors to go away)
