Re: [jetty-user] Fail to embed Jetty in a bundle

The aggregates are not osgi bundle capable. (nor will they likely ever be
as osgi doesn't like 2 different artifacts advertising the same content
from different coordinates)
Sorry.

Any bundle-like information in the meta-inf/manifest.mf you find in them is
purely a side-effect of the aggregation process and a complete accident.
For osgi related work, you'll likely want to start with the jetty-osgi
packages and work your way through the standard dependency list from there.

--
Joakim Erdfelt
[email protected]

http://webtide.com | http://intalio.com
(the people behind jetty and cometd)



On Mon, Feb 27, 2012 at 4:43 AM, Peter Nerg <[email protected]> wrote:

> I'm trying to embed the entire Jetty in a bundle of my own, i.e. not to
> install Jetty as separate bundles.
>
> I'm using one of the aggregate jars provided by Jetty and simply include it
> into my bundle that is built using maven.
> I've included all the dependencies provided in the following package:
> <dependency>
>        <groupId>org.eclipse.jetty.aggregate</groupId>
>        <artifactId>jetty-all-server</artifactId>
>        <version>7.6.1.v20120215</version>
>        <scope>compile</scope>
> </dependency>
>
>
> However when I try to start my bundle I get:
> /Unable to resolve 5.0: missing requirement [5.0] osgi.wiring package;
> (osgi.wiring.package=org.mortbay.log)/
>
> Not sure why it requests the mortbay logger as from what I gather it should
> no longer be used starting from v7 of jetty.
>
> --
> View this message in context:
> http://jetty.4.n6.nabble.com/Fail-to-embed-Jetty-in-a-bundle-tp4514503p4514503.html
> Sent from the Jetty Support mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>