Creating Eclipse help from within Eclipse
This topic explains how to create an Eclipse help documentation
plug-in from within the Eclipse platform. This process allows you
to set up repeatable builds directly within Eclipse, which may already
be familiar to many developers working within Eclipse. The topic was
originally written based on Eclipse 3.3, but much of the information
still applies.
- Create a new PDE project in Eclipse, and apply the DITA template to the project by following the wizard.
- Set the source directory, the main ditamap file, the output directory (default value
is root directory of project), css storage directory (used to contain
common.css
,commonltr.css
, andcommonrtl.css
), user customized .css file name, and conditional processing ditaval file in the wizard. Use root as output directory is selected as the default. - Create DITA files in the source directory and a ditamap to include the topic files that you created.
- Import the DITA files into the
src
directory of the DITA plug-in project you just created.- Right-click a directory that you want to put the imported files and select .
- Select the directory under which you put the DITA files.
- Click Finish after you selected the DITA files under the specified directory. The DITA files are then imported to your DITA project.
- Right click
build.xml
, select .Note
If you're using Oracle JDK, please download and use the latest Xalan. The Xalan shipped with Oracle JDK has some issue that will cause the build failure. You can use the latest Xalan by selecting ANT Build ... and include the all of Xalan's jar files in Classpath. - Edit the plug-in description of the property file
MANITEST.MF
in the plug-in editor after you run the Ant build successfully.- Click
MANITEST.MF
to go to the Overview page. - Edit Dependencies to include
org.eclipse.help
. - Edit Extensions to add
org.eclipse.help.toc
; right click the addedorg.eclipse.help.toc
, and select . - Edit the Build Configuration to include the out directory or the directory you specified in .
- Save the changes you made to the property file MANITEST.MF.
- Click
- Export the output to a documentation plug-in.
Note
build.xml can be customized to meet the requirement of headless build.- Select Deployable plug-ins and fragments and click Next. ; select
- Select the plug-in you want to export and specify a directory under which you want to put the plug-in package.
- Click Finish to export the plug-in package.