The target platform defines the set of bundles and features that you are developing against.

The target platform defines the set of bundles and features that you are developing against.

−

===== Defining the target platform the easy way =====

+

===== Defining the target platform the easy way =====

−

SMILA ships a target definition file at http://dev.eclipse.org/svnroot/rt/org.eclipse.smila/trunk/releng/devenv/SMILA-indigo-SR1.target that you can open in your IDE (after downloading it and importing the releng project; if you downloaded the source code using the Project Set File you will already have the SMILA.releng project containing the target definition in your workspace).

+

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 Indigo SR1 (3.7.1):

−

This file contains all the references needed for developing SMILA with Eclipse Indigo SR1 (3.7.1). After opening it, eclipse starts to download the referenced bundles/features which it tells you by stating "resolving target platform" in the status bar. This takes a good while. After it is done you can hit the link "Set as Target Platform" on the top left of the editor. Doing so will cause eclipse to start re-compiling the sources and all error markers should be gone.

+

#If the <tt>SMILA.releng</tt> project is not already contained in your workspace (e.g. because you have chosen the manual way to check out and import the source files), check out [http://dev.eclipse.org/svnroot/rt/org.eclipse.smila/trunk/releng http://dev.eclipse.org/svnroot/rt/org.eclipse.smila/trunk/releng] with your preferred SVN client and import the project into your workspace.<br>

+

#Open the file <tt>SMILA.releng/devenv/SMILA-indigo-SR1.target</tt> with the ''Target Definition'' editor. <br>

+

+

Eclipse starts downloading the referenced bundles/features which it tells you by stating "resolving target platform" 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 =====

===== Defining the target platform manually =====

Revision as of 10:45, 18 January 2012

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

Preconditions

Getting the source code

There is more than one way of getting the code into your Eclipse workspace. In the next two sections, two recommended ways are shown. After having imported the source code into your workspace, it will show up a lot of errors. Don't worry, they'll disappear when you run through all steps of this HowTo.

Both methods descibed below will lead you to the same result: They will provide you with a workspace containing all core SMILA projects (plus SMILA.releng when you choose the Project Set File).

Getting the source code manually

Getting the source code manually without the Project Set File is the recommended practice, especially when you wish to update frequently.

Use your favorite SVN client to check out SMILA's source code from the repository located at:http://dev.eclipse.org/svnroot/rt/org.eclipse.smila/trunk/coreHint: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.

After having checked out the source code, import it into your workspace:

Click Finish.Now your IDE starts to download and import the SMILA projects. This will take quite a while.

Hint:When you want to reimport the .psf file (e.g. because there are new projects available in the SMILA core repository), you have to update the .psf file in the SMILA.releng project and import it (right click on it 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.

Enabling the BPEL Designer

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:

Defining the target platform

The target platform defines the set of bundles and features that you are developing against.

Defining the target platform the easy way

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 Indigo SR1 (3.7.1):

Open the file SMILA.releng/devenv/SMILA-indigo-SR1.target with the Target Definition editor.

Eclipse starts downloading the referenced bundles/features which it tells you by stating "resolving target platform" 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

Launch 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.

Make sure that there aren't any junit 4 bundles activated:

Enter "junit" into the filter text field.</span

Uncheck all junit 4 bundles (e.g. org.junit4, org.junit(4.8.2....) etc.) because they conflict with the junit 3 bundles used in SMILA.

Click Debug. If everything works fine, you will get an output in the Console view similar to the following: