Re: [jetty-user] Re: Fail to embed Jetty in a bundle
Hugues Malphettes <[email protected]> Tue, 28 Feb 2012 09:46:33 +0800
| Newsgroups | gmane.comp.java.jetty.support |
|---|---|
| Message-ID | <CAPat9Ym_hkUq4brZOuzqPamF7txa1JZtpetCpAQnfDXD-08yhw@mail.gmail.com> |
Hi Petr and Jesse, In fact one of the aggregate "jetty-all-server" is OSGi-abled. Dmytro requested and assisted us with it. Here is the bug where the work was done: https://bugs.eclipse.org/bugs/show_bug.cgi?id=317222 I am not sure where the import for org.mortbay would come. Please let us know if we need to change something in the build of "jetty-all-server" to fix it or accommodate your situation. Cheers, Hugues. On Mon, Feb 27, 2012 at 10:14 PM, Jesse McConnell <[email protected]> wrote: > if you are close with your approach I don't see it being a bad thing > > I had thought the aggregates were 'close' for osgi and were being > adjusted for supporting that, at least at some point in their history > they were > > since your trying to generate a large bundle of your own then I would > probably look at using the same sort of dependency setup as the > aggregate pom and roll your own manifest, no reason that wouldn't work > > it will be 'un-osgi' but that isn't necessarily a bad thing :) > > cheers, > jesse > > -- > jesse mcconnell > [email protected] > > > > On Mon, Feb 27, 2012 at 08:07, Peter Nerg <[email protected]> wrote: >> Really! >> >> That's odd, if I install the aggregate and a few other bundles into Felix >> and then add my own bundle it simply works...:) >> >> However when putting the jetty bundle + a few others into my own bundle it >> fails. >> >> Anyways I'll drop that track and take a look at the "proper" OSGi bundles >> for Jetty. >> That's what I get for trying to save time with one big happy binary..:( >> >> -- >> View this message in context: http://jetty.4.n6.nabble.com/Fail-to-embed-Jetty-in-a-bundle-tp4514503p4514912.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 >> >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email