Including the Eclipse 3.3 help system in RCP applications

19

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):

  • javax.servlet
  • javax.servlet.jsp
  • org.apache.commons.el
  • org.apache.commons.logging
  • org.apache.jasper
  • org.apache.lucene
  • org.apache.lucene.analysis
  • org.eclipse.core.variables
  • org.eclipse.equinox.http.jetty
  • org.eclipse.equinox.http.registry
  • org.eclipse.equinox.http.servlet
  • org.eclipse.equinox.jsp.jasper
  • org.eclipse.equinox.jsp.jasper.registry
  • org.eclipse.help.appserver
  • org.eclipse.help.base
  • org.eclipse.help.ui
  • org.eclipse.help.webapp
  • org.eclipse.osgi.services
  • org.motbay.jetty

19 Comments

  1. MarkusSeptember 4, 2007

    Hi,

    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.

    Cheers
    Markus

  2. Kai TödterSeptember 4, 2007

    Hi Markus,

    actually I did the same and would consider it a good idea to provide a standard help feature for further reuse.

  3. MatthiasSeptember 4, 2007

    Thanks Kai. Very useful!

  4. Boris BokowskiSeptember 4, 2007

    Creating a feature sounds like a good idea. Did you file a bug for this? Could you add me to the cc list? Thanks!

  5. Wayne BeatonSeptember 4, 2007

    Kai, can you raise a bug against the “help” documentation?

  6. Nicolas RichetonSeptember 4, 2007

    Hi

    +1 I also did the same. You should create a bugzilla entry for this.

    Nicolas

  7. Kai TödterSeptember 4, 2007

    I have filed a feature request (bug id 202160) and a documentation bug (bug id 202159)

  8. leuiscSeptember 29, 2007

    Hi

    Very much for a long time searched for article on this theme.Thanks.
    by

  9. leuiscOctober 4, 2007

    Hello
    I was very much helped by the information with this article.
    Many thanks at you very fascinating resource.
    by

  10. WahooOctober 7, 2007

    Thank you for sharing!

  11. MartinFebruary 14, 2008

    There is a typo, it should be: org.eclipse.core.variables

  12. Kai TödterFebruary 14, 2008

    Thanks, typo fixed.

  13. RockoApril 24, 2008

    And mortbay instead of motbay.
    thx a lot

  14. RockoApril 24, 2008

    org.eclipse.ui.forms is missing (here)

  15. JMFebruary 26, 2009

    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.

  16. Kai TödterMarch 4, 2009

    JM,

    in Eclipse 3.4 there is a help feature included, don’t make your own.

  17. Adding Help to Eclipse 3.3 RCP Applications :: Modular MindJuly 31, 2009

    […] The Eclipse help system changed dramatically in Eclipse 3.3, and it requires a new set of plug-ins to work correctly. There is little documentation about how to include the help system in an RCP application, though Kai Tödter was kind of enough to post a list of the correct help system plug-ins.  […]

  18. Henno VermeulenJuly 5, 2011

    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?

    • Kai TödterJuly 5, 2011

      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.

Leave a Reply

I accept the Privacy Policy