| org.mortbay.jetty.* dependencies for the help system [message #631827] |
Fri, 08 October 2010 19:30  |
Eclipse User |
|
|
|
I am trying to set up a help system for my RCP app. I am using 3.5SR2 as my platform.
We have a custom target platform based on the RCP Runtime, Delta pack and EMF (among other things).
Following some docs I read, I added some dependencies for the help system, namely:
org.eclipse.help.ui
org.eclipse.help.webapp
org.eclipse.equinox.http.jetty
This set off a cascade of additional unsatisfied dependencies. Most I was able to get from the Eclipse platform plugins directory; a few others came from the plugins dir of the JEE eclipse version. However, the org.eclipse.equinox.http.jetty plugin has the following dependencies:
org.mortbay.component; version="[6.1.0,7.0.0]"
org.mortbay.jetty; version="[6.1.0,7.0.0]"
org.mortbay.jetty.bio; version="[6.1.0,7.0.0]"
org.mortbay.jetty.handler; version="[6.1.0,7.0.0]"
org.mortbay.jetty.nio; version="[6.1.0,7.0.0]"
org.mortbay.jetty.security; version="[6.1.0,7.0.0]"
org.mortbay.jetty.servlet; version="[6.1.0,7.0.0]"
org.mortbay.log; version="[6.1.0,7.0.0]"
I went to the jetty website and based on the docs it seems odd that the org.eclipse.equinox.http.jetty plugin would depend on org.mortbay.* bundles because the org.eclipse.equinox.* is the new naming convention and the org.mortbay.* is the old convention.
Regardless of that apparent inconsistency, can someone tell me where to get these plugins?
Or have I done this wrong? Is there some other way of setting up a help system in my RCP app that is less involved?
These apparent missing dependencies get reported when I validate my run configuration of my app.
Thanks,
Jon
|
|
|
|
|
| Re: org.mortbay.jetty.* dependencies for the help system [message #632136 is a reply to message #631827] |
Mon, 11 October 2010 13:11  |
| Eclipse User |
|
|
|
For anyone else who is looking, here is the complete list of plugins I had to add to my target platform to get the help working. This is for Galileo (3.5 SR2), so for other platforms the versions may vary:
javax.servlet.jsp_2.0.0.v200806031607.jar
javax.servlet_2.5.0.v200806031605.jar
org.apache.commons.el_1.0.0.v200806031608.jar
org.apache.commons.logging_1.0.4.v201005080501.jar
org.apache.jasper_5.5.17.v200903231320.jar
org.apache.lucene.analysis_1.9.1.v20080530-1600.jar
org.apache.lucene_1.9.1.v20080530-1600.jar
org.eclipse.equinox.http.jetty_2.0.0.v20090520-1800.jar
org.eclipse.equinox.http.registry_1.0.200.v20090520-1800.jar
org.eclipse.equinox.http.servlet_1.0.200.v20090520-1800.jar
org.eclipse.equinox.jsp.jasper.registry_1.0.100.v20090520-18 00.jar
org.eclipse.equinox.jsp.jasper_1.0.200.v20090520-1800.jar
org.eclipse.help.base_3.4.0.v200906111540.jar
org.eclipse.help.ui_3.4.0.v20090528.jar
org.eclipse.help.webapp_3.4.0.v20090429_1800.jar
org.eclipse.osgi.services_3.2.0.v20090520-1800.jar
org.mortbay.jetty.server_6.1.15.v200905151201.jar
org.mortbay.jetty.util_6.1.15.v200905182336.jar
Again, this is only in the case where you are building your target platform from scratch. If you use the whole SDK or the default runtime, this is not applicable.
HTH,
Jon
|
|
|
Powered by
FUDForum. Page generated in 0.07534 seconds
Home