Hi Dave,
On 08/04/11 08:50, Dave Reynolds wrote:
Thorsten wrote:
Anyway, is it really necessary to have an extra JAR with the OSGi
meta data (and one without)? As far as I can see, the set of
classes would not change in that extra JAR (would it?), only the
manifest.mf would be enriched by additional OSGi meta data. The
latter is unproblematic as non-OSGi environments would just ignore
it. Do I miss something?
We are talking about having a (reasonably) self-contained
jena-bundle which will include the most/all of the dependent jars
that end up in the lib part of the jena distribution (i.e. icu4j,
stax etc). That way you can just drop the jena-bundle into your
container and you are all set.
It is perfectly possible to do what Paolo has already done and
include an OSGi manifest in the jena.jar. That is useful but not as
useful having a more self contained bundle.[*]
Sorry, I must be missing something here. I thought that the point of
OSGI was like maven and other dependency managers: that the dependencies
are declarative so that (a) they can be auto-installed by the container,
and (b) duplication can be avoided and conflicts resolved. Are you
saying that in an OSGI container, you're still responsible for
installing all the dependencies yourself?
> [*] Caveat I've been working with OSGi for barely a week so I'm hardly
> an expert on it, though other projects seem to go a similar way.
And I have no experience at all, apart from the talk you gave at work!
Ian
--
____________________________________________________________
Ian Dickinson Epimorphics Ltd, Bristol, UK
mailto:[email protected] http://www.epimorphics.com
cell: +44-7786-850536 landline: +44-1275-399069
------------------------------------------------------------
Epimorphics Ltd. is a limited company registered in England
(no. 7016688). Registered address: Court Lodge, 105 High St,
Portishead, Bristol BS20 6PT, UK
