- Documentation (2.5.0-local-20170911195251)
- Release Notes
- Settings Files
- Ivy Files
- Ant Tasks
- post resolve tasks
- Using standalone
- Developer doc
Building a standard OSGi bundle
Note that this feature is considered as experimental.
TODO - WORK IN PROGRESS
This page describes how to build an OSGi bundle with Apache Ivy. In this use case, we just basically want to compute a classpath to compile, optionally one for testing too, and then publish our bundle in a OSGi aware repository.
In order to produce OSGi metadata of sufficient quality and to avoid maintaining them manually, the bnd tool will be used. The approach taken is then an "Ivy file first" approach. The dependencies will be specified in the
ivy.xml file, the
MANIFEST.MF being generated from the computed classpath.
In few steps, we will setup a build to compile and publish an OSGi bundle.
ivysettings.properties, specify the location of the plugins folder of your Eclipse target
(optional) by default the
build.xmlis expecting the sources to be in the
srcfolder. You may want to edit it if it is not the case
(optional) if Ivy is not in Ant’s classpath, download the Ivy jar and edit the
build.xmlaccordingly (see the comments at the beginning of the file)
To build the project, run: