Shibboleth Developers

[Jonathan Tellier <>]

> So, I guess one place to start is to talk about tooling a bit.

OK, well as far as tooling goes, here's what I've used to bundle the
IdP. Note that since it's my first big project involving OSGi, it's
hard for me to do any meaningful comparisons.

In the project on which I'm working on, we're using Fuse ESB 4.3
(http://fusesource.com/products/enterprise-servicemix/). Fuse uses
Apache Karaf (http://karaf.apache.org/), a runtime that provides both
an OSGi container and some tools on top of it. By default the OSGi
container used by that project is Equinox, but Felix is also supported
(http://karaf.apache.org/how-do-i-choose-between-felix-and-equinox.html).
Since the stuff we're working on is not implementation-dependant,
we've seen no reason to switch from the default.

In order to create the bundle, I've used the Bundle Plugin for Maven
(http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html).
This tools is based on bnd (http://www.aqute.biz/Code/Bnd) and it
eases the process of creating bundles by, for instance, scanning the
project's code and automatically determining what dependencies are
needed by the project.

> In particular I'm very concerned about
> management of the exported APIs list in the manifest.  I have no interest in
> trying to maintain that manually.

I'm not sure I understand what you mean. A list of private and
exported packages will have to be defined somewhere. With the Maven
Bundle Plugin, those are defined within the POM file used to generate
the manifest. Is that too much of a manual process?

Jonathan