I just updated the help system for one of my tutorial RCP applications to Eclipse 3.3. I wanted to use the Jetty stack instead of Tomcat, like the Eclipse 3.3 SDK does. Since the help on “RCP help” is still a bit outdated, it took me a while to collect all necessary plug-ins. Here is the list of plug-ins you need to deploy with your Eclipse 3.3 RCP based application if you want to use the Jetty stack (in alphabetical order):
This Post Has 19 Comments
I wonder if it makes sense to create an “official” org.eclipse.help feature which contains all these dependencies (like org.eclipse.rcp). We have created our own, after we spent quite some time figuring out what’s required too.
actually I did the same and would consider it a good idea to provide a standard help feature for further reuse.
Thanks Kai. Very useful!
Creating a feature sounds like a good idea. Did you file a bug for this? Could you add me to the cc list? Thanks!
Kai, can you raise a bug against the “help” documentation?
+1 I also did the same. You should create a bugzilla entry for this.
I have filed a feature request (bug id 202160) and a documentation bug (bug id 202159)
Very much for a long time searched for article on this theme.Thanks.
I was very much helped by the information with this article.
Many thanks at you very fascinating resource.
Thank you for sharing!
There is a typo, it should be: org.eclipse.core.variables
Thanks, typo fixed.
And mortbay instead of motbay.
thx a lot
org.eclipse.ui.forms is missing (here)
Hi, I am working on an RCP application development and have tried quite a bit to get the help system running but inspite of including all these plugins mentioned above, the help contents just dont show up. Any suggestions. I am using Eclipse 3.4.
My product file contains all these plugins. Am i missing on something here.
in Eclipse 3.4 there is a help feature included, don’t make your own.
Pingback: Adding Help to Eclipse 3.3 RCP Applications :: Modular Mind
Thank you for getting Eclipse to get this help feature! I have included it in my target platform and added the feature to my own feature on which my product configuration is based.
Now I am having a small problem: I already included version 1.1.1 of commons logging to my target platform and my feature and I do not want to use the older 1.0.4 version (because together with log4j it converts TRACE to DEBUG).
But when I include the help feature in my own feature, I automatically get the two versions of commons logging and the older version is used at runtime for all plugins that use logging. I use PDE build through the wizard and don’t want to include both plugins.
I guess I will have to make my own help feature? Or do you happen to know of another way?
just specify a different dependency version range for the commons logging bundle in your bundles. As long as an OSGi bundle is not dclared to be a singleton you can have multiple versions running.