</div> <br> Ignore the warning stating that the bundle cannot be resolved. It is generated automatically at build time.

+

</div>

−

+

:Ignore the warning stating that the bundle cannot be resolved. It is generated automatically at build time.

* In your bundle, be sure to add at least the <tt>META-INF</tt> directory, the <tt>about</tt> files and the <tt>build.properties</tt> to the build configuration of the source build. Add additional files (schemas, sample configs, etc) as appropriate. Do NOT add the <tt>code/src</tt> or other source directories, this is done automatically by the build process: <br> [[Image:SMILA-bundle-source-build-properties.png|600 px]]

* In your bundle, be sure to add at least the <tt>META-INF</tt> directory, the <tt>about</tt> files and the <tt>build.properties</tt> to the build configuration of the source build. Add additional files (schemas, sample configs, etc) as appropriate. Do NOT add the <tt>code/src</tt> or other source directories, this is done automatically by the build process: <br> [[Image:SMILA-bundle-source-build-properties.png|600 px]]

[[Category: SMILA]]

[[Category: SMILA]]

Revision as of 09:09, 25 January 2012

The following steps have to be done to integrate a new bundle (plug-in) in the SMILA build process:

Include new plug-in into org.eclipse.smila.feature

To include your plug-in:

Open the feature.xml file of the project org.eclipse.smila.feature in the Feature Manifest Editor.

Switch to the Plug-ins page and add the bundle to the Plug-ins and Fragments list. You don't have to adapt the Plug-in Details.

Useful Information
You don't have to modify the build file (make.xml) to include your bundle in the build process.
The make.xml file includes all SMILA bundles located under the local trunk folder, along with those bundles whose names match its <patternset> elements (com.*, net.* and so on). If you get an error such as "Unable to find bundle xxx", it's probably because it is not matched by make.xml and it is not copied to the build folder. If you don't want to include your new bundle into the build process, the bundle has to be excluded explicitly in make.xml. For further information see: Introduction to make.xml.

Optional step: Generate Source Bundle

The build process can also generate an additional source bundle for a new bundle so that debugging is easier when SMILA is used as a target platform (see How to set up the integration environment). This needs some manual modification of the files of the feature that includes the bundle:

In org.eclipse.smila.feature/build.properties add a line like this using the bundle name of your new bundle:

Ignore the warning stating that the bundle cannot be resolved. It is generated automatically at build time.

In your bundle, be sure to add at least the META-INF directory, the about files and the build.properties to the build configuration of the source build. Add additional files (schemas, sample configs, etc) as appropriate. Do NOT add the code/src or other source directories, this is done automatically by the build process: