Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

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

(Define target platform)
Line 26: Line 26:
  
 
Click File --> Import --> General --> Existing Projects into Workspace --> Next --> Select root folder of local trunk --> Finish
 
Click File --> Import --> General --> Existing Projects into Workspace --> Next --> Select root folder of local trunk --> Finish
 +
 +
{{note|Currently we have two bundles in the trunk that won't compile in the workspace when configured as described here:
 +
* org.eclipse.smila.processing.designer.model
 +
* org.eclipse.smila.processing.designer.ui
 +
To compile these you need bundles from the [http://www.eclipse.org/bpel Eclipse BPEL Designer] in your target platform. See [SMILA/BPEL_Designer] for more information on these bundles.
 +
}}
  
 
==== Define target platform  ====
 
==== Define target platform  ====

Revision as of 10:26, 18 January 2011

This how-to describes the necessary steps for setting up SMILA development environment. Normally this setup is only interesting for SMILA committers and contributors. SMILA integrators should work with another setup described at How to set up the integration environment.


Preconditions

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

  1. JDK 1.6
  2. current Eclipse SDK - This how-to was tested with Eclipse Classic SDK 3.5 (Galileo)
  3. The source code

Note: If you want to use SMILA source code from before its migration to 3.5 you will also need to use 3.4.2 Eclipse as your IDE. Simply using the correct target platform from within Galileo wont work. See how this is done at Dev Env Setup for Eclipse 3.4.2 (Ganymede)

Get the source code

Use your favorite SVN client to check out SMILA's source code from repository located at:

http://dev.eclipse.org/svnroot/rt/org.eclipse.smila/

Hint:

  • We recommend you to check out the whole repository or at least the trunk. By doing so you can easily get new projects just by updating the trunk and reimporting the sources.

Import sources into Eclipse IDE

After you have checked out the source code you need to import it in your IDE:

Click File --> Import --> General --> Existing Projects into Workspace --> Next --> Select root folder of local trunk --> Finish

Note.png
Currently we have two bundles in the trunk that won't compile in the workspace when configured as described here:
  • org.eclipse.smila.processing.designer.model
  • org.eclipse.smila.processing.designer.ui

To compile these you need bundles from the Eclipse BPEL Designer in your target platform. See [SMILA/BPEL_Designer] for more information on these bundles.



Define target platform

The goal of this step is to use Eclipse IDE installation together with plug-ins from SMILA.extensions folder as the target platform.

  • Click Window --> Preferences --> Plug-in Development --> Target Platform
  • Click Add... --> Select "Default" for target initialization and click "Next"
Rename the new target, e.g. to "Running target + SMILA.Extension"
Click "Add..." --> Select "Directory" --> Click Next --> Select SMILA.extension/eclipse/plugins folder under local trunk as the location --> Click Finish
The target definition dialog should now look like this:

Target.PNG

Change to page "Environment" and select "JavaSE-1.6" as Execution Environment
Click "Finish" and activate the new target platform.

Launch SMILA in Eclipse IDE

If you've checked out SMILA's trunk correctly, than 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 Debug --> Debug Configurations and expand OSGI Framework
  • Select launch file for your environment and press Debug

Launch-smila.png


  • If everything is started correctly, you will get an output in the Console view like below:

Console.png

Back to the top