-
Notifications
You must be signed in to change notification settings - Fork 13
Setting up your Development Environment
Thomas Gossmann edited this page Apr 11, 2014
·
7 revisions
Setting up can be done in 2 ways.
- Minimum Installation: To develop on the composer-plugin
- Test Installation: To run the test suites
Eclipse Kepler (minimum) is required.
- m2e
- m2e connector for mavenarchiver pom properties
- Graphical Editing Framework Zest Visualization Toolkit SDK
Add the Orbit Update Site and install:
- Apache Commons Collections
- Apache Commons Exec
Add the Dubture Orbit Update Site and install:
- Dubture OSGI-Bundles
- From the PDT Extensions (Dev) Update Site, install:
- PDT Extensions
- Lucene Indexing
- Json Editor
- Clone Repositories and build them with maven in your workspace (Shell-Script):
* Rsp. your forks
- Import Projects into Eclipse
- Right click the Project Explorer and select "Existing Maven Projects"
- Select the folder in which both projects are located (pulse00 in this case, may be your username)
- Uncheck the
com.dubture.composer.test
project (this won't run due to dependencies, only works in complete install) - Click next and finish
- This may eventually bring up the Software Installation dialog for additional maven connectors, install them
- Run the Eclipse /w the Composer Editor
- Right-click the
com.dubture.composer.ui
project > Run As > Eclipse Application - Optimize your Run-Configuration: Near the "Run" icon in the toolbar, click the little triangle > Run Configurations ...
- Plugins Tab: Lauch with 'Plug-ins selected below', Deselect All, Check
com.dubture.composer.ui
, Hit the button "Add Required Plug-ins" on the right, Apply button at the bottom and Run. - Have fun :)
Same as Minimum Installation plus:
Add the DLTK Update Site and install:
- DLTK-Tests
Same as importing projects above, this time check the com.dubture.composer.test
project.
To run a test/the tests right-click either the package com.dubture.composer.test
or AllTests
or a particular test and select Run As ...
-> JUnit Plug-In Test
.
Use the com.dubture.composer.core.log.Logger
to write out debug messages. To read them:
- Open the launch configuration
- Tab 'Tracing'
- Enable Tracing (if not already)
- Check
com.dubture.composer.core
and check debug on the right
Now, your debug message will be readable from the Console view during the execution
From the Kepler Update Site:
- SWT Designer
From the Eclipse Project Update Site:
- Eclipse Platform SDK (for proper javadocs)