Skip to main content

Notice: This Wiki is now read only and edits are no longer 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"

(dev env)
(how to build and test locally)
Line 12: Line 12:
 
* set up an own Eclipse instance/installation for building
 
* set up an own Eclipse instance/installation for building
 
** - eg. eclipse-SDK-3.3-win32
 
** - eg. eclipse-SDK-3.3-win32
** - copy startup.jar[http://bugs.brox.de/confluence/download/attachments/11075968/startup.jar] from an older eclipse installation (< 3.3) into it's root
+
** - download eclipse-RCP-3.3.2-delta-pack.zip from [http://archive.eclipse.org/eclipse/downloads/drops/R-3.3.2-200802211800/index.php], unzip the archive and copy org.eclipse.equinox.executable from features into your features folder under your eclipse installation.
** - check is Native Launcher feature (see [http://www.eclipse.org/equinox/framework/]: "org.eclipse.equinox.executable") installed, if not, and add it with dependent plug-ins
+
** start that eclipse add sole extension location to WC /SMILA.extension by
** start that eclipse add sole extension location to WC /EILF.extension by
+
 
*** menue help - Software Updates - Manage configuration
 
*** menue help - Software Updates - Manage configuration
*** add extension location and choose the folder EILF.extension/eclipse from smila project folder
+
*** add extension location and choose the folder SMILA.extension/eclipse from smila project folder
* EILF.builder
+
* SMILA.builder
 
*: this is used to build and run all tests but before local usage it must be adapted.  
 
*: this is used to build and run all tests but before local usage it must be adapted.  
 
** build smila in eClipse
 
** build smila in eClipse
*** select the EILF.builder bundle
+
*** select the SMILA.builder bundle
 
*** open External Tools Dialog
 
*** open External Tools Dialog
 
*** create a new ant build configuration or choose your configuration if exists
 
*** create a new ant build configuration or choose your configuration if exists
*** choose the buildfile of this bundle, e. g. ${workspace_loc:/EILF.builder/make.xml}
+
*** choose the buildfile of this bundle, e. g. ${workspace_loc:/SMILA.builder/make.xml}
 
*** insert the following arguments (but change this to your folder structure)
 
*** insert the following arguments (but change this to your folder structure)
***: -DbuildDirectory=D:/eccenca/eilf/eclipse.build  
+
***: -DbuildDirectory=D:/eccenca/smila/eclipse.build  
 
***: -Declipse.home=D:/eclipse33  
 
***: -Declipse.home=D:/eclipse33  
***: -Dbuilder=D:/eccenca/eilf/eilf.builder  
+
***: -Dbuilder=D:/eccenca/smila/SMILA.builder  
 
***: -Declipse.running=true  
 
***: -Declipse.running=true  
 +
***: –DpdeBuildPluginVersion=3.3.2.v20071019(default)
 +
***: –DequinoxLauncherPluginVersion=1.0.1.R33x_v200080118(default)
 
***: -Dos=win32 -Dws=win32 -Darch=x86
 
***: -Dos=win32 -Dws=win32 -Darch=x86
*** Apply, close and run EILF.builder with this external tool configuration
+
*** Apply, close and run SMILA.builder with this external tool configuration
** variante with EILF.builder\make.bat
+
** variante with SMILA.builder\make.bat
 
**: the make.bat is used by bamboo so dont update it unless u know what u are doing!
 
**: the make.bat is used by bamboo so dont update it unless u know what u are doing!
 
**:there is a template version of this with the ending .#~#~#. copy that over the make.bat or use another name to ur linking.
 
**:there is a template version of this with the ending .#~#~#. copy that over the make.bat or use another name to ur linking.
*** adjust all paths in \EILF.builder\make.bat according to own setup
+
*** adjust all paths in \SMILA.builder\make.bat according to own setup
 
** - execute make.bat
 
** - execute make.bat
  

Revision as of 04:12, 17 October 2008

Howto set up dev environment

dev env

how to build and test locally

  • set up an own Eclipse instance/installation for building
    • - eg. eclipse-SDK-3.3-win32
    • - download eclipse-RCP-3.3.2-delta-pack.zip from [1], unzip the archive and copy org.eclipse.equinox.executable from features into your features folder under your eclipse installation.
    • start that eclipse add sole extension location to WC /SMILA.extension by
      • menue help - Software Updates - Manage configuration
      • add extension location and choose the folder SMILA.extension/eclipse from smila project folder
  • SMILA.builder
    this is used to build and run all tests but before local usage it must be adapted.
    • build smila in eClipse
      • select the SMILA.builder bundle
      • open External Tools Dialog
      • create a new ant build configuration or choose your configuration if exists
      • choose the buildfile of this bundle, e. g. ${workspace_loc:/SMILA.builder/make.xml}
      • insert the following arguments (but change this to your folder structure)
        -DbuildDirectory=D:/eccenca/smila/eclipse.build
        -Declipse.home=D:/eclipse33
        -Dbuilder=D:/eccenca/smila/SMILA.builder
        -Declipse.running=true
        –DpdeBuildPluginVersion=3.3.2.v20071019(default)
        –DequinoxLauncherPluginVersion=1.0.1.R33x_v200080118(default)
        -Dos=win32 -Dws=win32 -Darch=x86
      • Apply, close and run SMILA.builder with this external tool configuration
    • variante with SMILA.builder\make.bat
      the make.bat is used by bamboo so dont update it unless u know what u are doing!
      there is a template version of this with the ending .#~#~#. copy that over the make.bat or use another name to ur linking.
      • adjust all paths in \SMILA.builder\make.bat according to own setup
    • - execute make.bat
  • the whole process takes about 15 minutes at the time of writing, so be patient or get some java-like beverage

run junit tests for osgi bundles

  • Plugin Junit Launch config
  • write config.ini and ref it from lauch config.
    tip: use \ to brake up long lines to have better overview
  • share the launch config

For further information see: Development Guidelines

Back to the top