### 21.6 Merging Eclipse Help projects

If your customers are using Eclipse version 3.4 or later, you can simply insert PI marker in DITA XML for links to secondary TOCs from the primary content. The secondary modules do not need to know where they are used, and if any are missing, the primary helpset still works without error. The missing TOC items are silently omitted. See §21.6.1 Linking primary content to secondary TOCs.

If you must support versions of Eclipse prior to Eclipse 3.4, you might have to use anchors in the primary TOC and links to those anchors from any secondary modules; see §21.6.2 Linking secondary TOCs to primary content (deprecated). For versions of Eclipse starting with Eclipse 3.4, this method is deprecated.

In this section:

§21.6.1 Linking primary content to secondary TOCs

§21.6.2 Linking secondary TOCs to primary content (deprecated)

Previous Topic: 21.5 Configuring search properties for Eclipse Help

Next Topic: 21.6.1 Linking primary content to secondary TOCs

Parent Topic: 21. Generating Eclipse Help

Sibling Topics:

21.1 Understanding how Eclipse Help works

21.2 Setting up an Eclipse Help project

21.3 Configuring Eclipse Help manifest files

21.4 Configuring contents and index for Eclipse Help

21.5 Configuring search properties for Eclipse Help

21.7 Setting up CSH for Eclipse Help

21.8 Packaging Eclipse Help files