Have you seen the documentation page: https://www.eclipse.org/jetty/documentation/9.2.6.v20141205/framework-jetty-osgi.html ?
For osgi, you can't necessarily use the javax.* jars from maven, as in my experience they often do not contain the correct manifests. If you follow the advice on the page above,you should be ok. Jan On 26 September 2015 at 05:27, Mark Leone <[email protected]> wrote: > Correction: I downloaded the javax.e1-3.0.0 jar. I mistakenly identified > it as the "jetty 3.0.0" jar. > > > On 09/25/2015 02:18 PM, Mark Leone wrote: > >> I have an RCP app that uses the jetty websocket client. It's been working >> fine with the jetty bundles packaged along with the code I developed, >> because I wasn't successful at getting them installed in my RCP target. Now >> I took the time to give it my best effort, and after hours of trying I >> reached a dead end. >> >> I read in this post ( >> https://dev.eclipse.org/mhonarc/lists/jetty-users/msg04454.html) that >> with the later versions of Jetty (I'm using 9.2.5) the required version of >> some dependencies are not included in equinox and also not available from >> orbit, so I need to download them myself and install them. I thought I did >> that correctly, but jetty is not satisfied. >> >> When I try to resolve my target with the jetty bundles included, it fails >> with this message: >> >> org.eclipse.jetty.osgi.boot.jsop 9.2.5.v20141112 requires 'package >> javax.el [3.0.0,3.1.0)' but it could not be found. >> >> So I downloaded the jetty 3.0.0 jar which contains package javax.el. I >> created a plug-in from this jar file, and named it javax.el with version >> 3.0.0. I exported the package javax.el on the run tab, and also tried >> specifying the package version as 3.0.0. >> >> Then I added a location to my target, pointing it at the folder which >> contains the jetty plug-in I created. When I look at the content tab of the >> target editor, I see see my plug-in there and it's selected. >> >> But I continue to get the same message in the target editor when I try to >> resolve the target. I believe I've successfully added the bundle I created >> to my target, but it's a package dependency that is failing. Am I supposed >> to do something further to make that package available? I don't know >> anything to do other than to export it. Are there other strategies I can >> use to get jetty working in my target? I don't find any useful discussion >> of people doing this when I searched the Internet, but surely I'm not the >> only one who is trying to use jetty in an RCP target. >> _______________________________________________ >> jetty-users mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> >> > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users > -- Jan Bartel <[email protected]> www.webtide.com *Expert assistance from the creators of Jetty and CometD*
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
