Swordfish Documentation: Adding Modules to Headless Build

Adding new modules

While it is easy to add new modules / projects to the SVN, there are some other places that need to be changed in order to include a new module into the build process.

This page should provide you minimal check lists depending on the type of module you want to add (feel free to contact Jürgen, Zsolt or Oliver if you are not sure - esp. if you might need to add a new feature!). Note also that check in of the map files will soon be restricted (not all committers will have write access to those files!). Please contact the person in charge of doing changes to those files.

Usually the changes will be limited to adding new entries to configuration files within the org.eclipse.swordfish.build project.

To add Core and plugin modules change

• the build.xml (see esp. target copy.sources.product)
• the swordfish.map
• the feature it belongs to (most probably org.eclipse.swordfish.feature)

To add Unit test modules change

• the build.xml (see esp. target copy.sources.test)
• the swordfish.map
• the org.eclipse.swordfish.tests feature

To add Integration test modules change

• the build.xml
• the swordfish.map

To add Sample modules change

• the build.xml (see esp. target copy.sources.product)
• the swordfish.map
• the org.eclipse.swordfish.samples feature

To add Third party modules

You need to contact Oliver / Zsolt in order to have a CQ filed for any new module that is not yet in Orbit.
If the bundle is in Orbit or the addition is approved, change

• the build.xml (see esp. target copy.sources.thirdParties)
• the swordfish.map
• the org.eclipse.swordfish.third-parties feature

Swordfish Contributor User Documentation
Swordfish Wiki Home