Skip to main content
Jump to: navigation, search

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

(how to build and test locally)
(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 from an older eclipse installation (< 3.3) into it's root
+
** - copy startup.jar[http://bugs.brox.de/confluence/download/attachments/11075968/startup.jar] from an older eclipse installation (< 3.3) into it's root
 
** start that eclipse add sole extension location to WC /EILF.extension
 
** start that eclipse add sole extension location to WC /EILF.extension
 
* EILF.builder\make.bat
 
* EILF.builder\make.bat

Revision as of 04:12, 12 September 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
    • - copy startup.jar[1] from an older eclipse installation (< 3.3) into it's root
    • start that eclipse add sole extension location to WC /EILF.extension
  • EILF.builder\make.bat
    • this is used to build and run all tests but before local usage it must be adapted. 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 \EILF.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