> I expect some integration tests to fail, because we'll need to embed many > additional OWL API packages: those two artifacts are enough for compiling, > but I'm afraid we're going to need a lot more for the ontologymanager to > work in the launcher, unless there is some readily available OSGi bundle for > the OWL API and its bindings. If not, is it OK if I use the commons.owl > bundle for embedding them?
I think commons.owl is the correct module to embed them. Just make sure to use "<_exportcontents>" instead of "<Export-Package>" for packages exported from embedded jar files. Also make sure that you add the correct "version" tags to exported packages. best Rupert > > Best, > Alessandro > -- | Rupert Westenthaler [email protected] | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
