Fix broken javadoc HTML tags in tycho-document-bundle-plugin

[Copilot]

Summary

This PR fixes malformed javadoc comments in the tycho-document-bundle-plugin that would cause javadoc generation tools to fail or produce warnings due to invalid HTML syntax.

Issues Fixed

Three javadoc syntax errors were identified and corrected:

1. Missing closing </code> tag in JavadocMojo.java (line 125)

The javadoc for the encoding parameter was missing the closing parenthesis inside the <code> tag:

// Before:
* <li><code>encoding</code>, used as javadoc <code>-encoding</code> parameter (default:
* <code>${project.build.sourceEncoding}</code></li>

// After:
* <li><code>encoding</code>, used as javadoc <code>-encoding</code> parameter (default:
* <code>${project.build.sourceEncoding}</code>)</li>

2. Missing closing </li> tag in JavadocMojo.java (line 174)

The javadoc for the mainFilename TOC option was missing the closing list item tag:

// Before:
* <li><code>mainFilename</code>, specifies the filename of the TOC file (default:
* "overview-summary.html")

// After:
* <li><code>mainFilename</code>, specifies the filename of the TOC file (default:
* "overview-summary.html")</li>

3. Incomplete javadoc comment in ConfigureMojo.java (line 24)

The class-level javadoc comment was incomplete, ending mid-sentence:

// Before:
/**
 * This mojo is only there
 */

// After:
/**
 * This mojo is only there to provide configuration parameters and should not be executed directly.
 */

Impact

These fixes ensure that:

• Javadoc generation tools can properly parse the documentation without errors
• HTML rendering of the javadoc is correct with properly matched tags
• The documentation is complete and meaningful for developers

All changes are minimal and focused solely on correcting the javadoc syntax without affecting any code behavior.

Original prompt

Fix broken javadoc

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[laeubi]

@waynebeaton as discussed in the EAC meeting this is the first item (and most likely an easy one), so I would say it falls in "Category A" not a problem and simply overrule the ECA check?

[github-actions]

Test Results

1 014 files  1 014 suites   6h 17m 39s ⏱️
1 297 tests 1 277 ✅ 20 💤 0 ❌
3 891 runs  3 828 ✅ 63 💤 0 ❌

Results for commit 3c6ca52.