| [equinox-dev] bundle builds using Maven |
|
My organization has been attempting to use the Maven build
process as described in the “Building Eclipse Plugins with Maven 2”
by the Princeton Softech guys to build a set of Equinox/OSGi bundles (not
Eclipse plugins.) I’ve successfully gotten a single bundle to build
but am having problems with cross-bundle dependencies. I have an aggregator/super-pom
that contains two modules – A and B. B, as defined in the manifest,
depends on A. A builds fine, but when B attempts to build it can’t
find A to build against. Is this situation supposed to work? I’ve made a slight modification to the Princeton Softech
Maven plugin that uses the bundle package “prefix” as the group Id
(i.e. com.company.product.bundle would use “com.companyu.product”
as the group id.) When the build errors out due to failed dependency
resolution it is looking for the artifact that I would expect it to (group id
and artifact id look correct.) The compilation can resolve the Equinox (3.3M7) bundles from
the manifest (using the group id change described above) and can find the
artifacts in the repo without issue. It is just this cross-module
building issue that I’m having. A related question I have is what is the common method of
building equinox bundles? Do most people just use the PDE tools included
in Eclipse? -Aaron |