Jump to: navigation, search

Difference between revisions of "SMILA/Documentation/HowTo/Howto set up dev environment"

m (Getting the source code)
Line 19: Line 19:
 
* Install ''Subversive SVN Team Provider'' and ''Subversive SVN JDT Ignore Extensions'' from the Eclipse software repository.<br>  
 
* Install ''Subversive SVN Team Provider'' and ''Subversive SVN JDT Ignore Extensions'' from the Eclipse software repository.<br>  
 
* Restart Eclipse.  
 
* Restart Eclipse.  
* Select ''Windows &gt; Preferences &gt; SVN''. This should open the ''Subversive Connector Discovery'' window.  
+
* Select ''Windows &gt; Preferences &gt; Team &gt; SVN''. This should open the ''Subversive Connector Discovery'' window.  
 
* Select the Subversive SVN Connector that you wish to use. We suggest to take the latest SVN Kit that is offered. At the time of writing it was SVN Kit 1.3.5.  
 
* Select the Subversive SVN Connector that you wish to use. We suggest to take the latest SVN Kit that is offered. At the time of writing it was SVN Kit 1.3.5.  
  

Revision as of 05:28, 16 July 2012


This HowTo describes the necessary steps for setting up a SMILA development environment.

Preconditions

Here is the list of things that you will definitely need for developing SMILA components:

Getting the source code

There is more than one way of getting the code into your Eclipse workspace. The following sections will describe how to get the source code via SVN (recommended!).

As a (non-recommended) alternative, you could download the complete source code from the release download page or the nightly build downloads and unpack the archive into your workspace.

Installing SVN Provider

(skip this section if SVN Team Provider is already installed in your eclipse IDE)

  • Install Subversive SVN Team Provider and Subversive SVN JDT Ignore Extensions from the Eclipse software repository.
  • Restart Eclipse.
  • Select Windows > Preferences > Team > SVN. This should open the Subversive Connector Discovery window.
  • Select the Subversive SVN Connector that you wish to use. We suggest to take the latest SVN Kit that is offered. At the time of writing it was SVN Kit 1.3.5.
Get source code from SVN

There are two ways for this, automatically by using the Project Set File or manually. Both are described in the following:

manually checking out and importing the projects:

Hint: We recommend to check out the trunk/core as opposed to importing the projects through IDE SVN integrations. By doing so, you can easily get new projects just by updating your working copy and reimporting the sources.
  • Import all SMILA project into your workspace:
    • Click File > Import > General > Existing Projects into Workspace > Next.
    • Select the folder that contains all SMILA projects --> (all projects should be selected automatically) > Finish.

automatic checkout and import by using the Project Set File:

  • Checkout ../org.eclipse.smila/trunk/releng
  • Right click on SMILA.releng/devenv.SMILA-core.psf
  • Click Import Project Set... and choose "No To All"
Hint:: New projects should always be added to the .psf file so you can import them (as before): right click on .psf file and click on "Import Project Set...", be sure to click "No To All" to the question whether to overwrite existing projects in the workspace, otherwise it will check out everything again instead of ignoring the projects, that are already checked out. If projects are removed you have to remove them manually from the workspace, this can't be handled via .psf file.

After having imported the source code into your workspace, it will show up a lot of errors. Don't worry, they'll disappear after the next steps below.

Enabling the BPEL Designer (optional)

If you want to work with the SMILA extensions for Eclipse BPEL designer, you need to check out the bundles from trunk/tooling. Currently, the required bundles are:

  • org.eclipse.smila.processing.designer.model
  • org.eclipse.smila.processing.designer.ui

To compile them you need additional bundles from the Eclipse BPEL Designer in your target platform. See SMILA/BPEL Designer for more information.

Defining the target platform

The target platform defines the set of bundles and features that you are developing against. SMILA ships a Target Definition File that you can open in your IDE to configure the target platform automatically. This file contains all the references needed for developing SMILA with Eclipse Juno (Release 4.2).

Using the target platform provided by SMILA
  • Checkout ../org.eclipse.smila/trunk/releng (if you haven't already done before)
  • Open the file SMILA.releng/devenv/SMILA.target with the Target Definition editor.
    Eclipse starts downloading the referenced bundles/features which it tells you by stating "Resolving Target Definition" in its status bar. Be patient, this will take quite a while. After it has finished, you can click the link "Set as Target Platform" on the top right of the Target Definition editor. Doing so will cause Eclipse to start re-compiling the sources and all error markers should be gone when finished.
Defining the target platform manually

Delta Pack

(only needed for building the software outside of eclipse IDE)

For building the software you may need to add a "Delta Pack" to an Eclipse SDK installation. You can download it from the here. After downloading, you can copy the contained plugins and features in your eclipse installation.

Checkstyle configuration

If you have the Eclipse Checkstyle plugin installed, you will get a lot of error messages complaining about missing check configurations when Eclipse builds the workspace. (Hint: For installing the Checkstyle plugin, use location: "http://eclipse-cs.sf.net/update/")

Errors running builder 'Checkstyle Builder' on project 'org.eclipse.smila.utils'.
Fileset from project "org.eclipse.smila.utils" has no valid check configuration.
...

You can solve this by importing them:

  • Open Window -> Preferences and go to Checkstyle.
  • Click New..., enter SMILA Checkstyle as the name, click Import..., and select SMILA.builder/checkstyle/smila_checkstyle-5.xml from your workspace. Click OK.
  • Click New... again, enter SMILA Test Checkstyle as the name, click Import..., and select SMILA.builder/checkstyle/smila-test_checkstyle-5.xml from your workspace. Click OK.
  • Select SMILA Checkstyle and click Set as Default.
  • Click OK.
    Now you should not get those error messages again.

Launching SMILA in Eclipse IDE

If you've checked out SMILA's trunk correctly, you should have a project called SMILA.launch in your workspace. This project contains the SMILA's launch configuration for Eclipse IDE. To start SMILA directly in your Eclipse IDE, just follow the steps below:

  • Click Run--> Debug Configurations and expand OSGI Framework.
  • Select the SMILA launch file.
  • Click Debug.
    If everything works fine, you will get an output in the Console view similar to the following:
osgi> Persistence bundle starting...
ProviderTracker: New service detected...
ProviderTracker: Added service org.eclipse.persistence.jpa.osgi.PersistenceProviderOSGi
Persistence bundle started.
[INFO ] Context /zookeeper: Registered handler(1) ZooKeeperAdminHandler, pattern /(.*)$
[INFO ] Added worker webFetcher to WorkerManager.
...
[INFO ] HTTP server has SMILA handler RequestDispatcher for context /smila.
[INFO ] HTTP server started successfully on port 8080.

You're done

Congratulations! You've just successfully checked out and configured your SMILA development environment and you can now start developing your own bundles.