[joaodinissf]

Why the change

Projects that write Check catalogs can now generate the catalogs' HTML documentation and Eclipse Help files in a normal Maven build, without an Eclipse workbench.

Special things to note

• The IDE builder still writes toc.xml and contexts.xml through PDE. For the repository's catalogs the templates write the same files the IDE builder last committed, and the test compares with those; it doesn't run PDE. Moving the IDE builder onto the templates is left for a follow-up.
• The application owns its output: it deletes other pages in docs/content/ and rewrites toc.xml and contexts.xml in full, where the IDE builder merges into them. The guide says so.
• The catalog pages change for IDE users too: self-contained HTML5 with inline CSS. check.css stays in check.runtime.ui, so pages generated by earlier releases keep their styling.
• check.core moves to 17.4.0, because it exports the new com.avaloq.tools.ddk.check.standalone package.
• The restyle of the catalog pages is its own commit and could be split into a separate PR if preferred; the golden files and committed docs are in the new style.

Change outline

A new Eclipse application, com.avaloq.tools.ddk.check.core.docApplication, turns a source folder into a docs/ tree. It fails without writing anything when something is wrong:

CheckDocApplication.generate(sourceDir, docsDir)
  findCheckFiles(sourceDir)            # skips target/ and dot-folders below sourceDir only
  load each .check file
    syntax errors?  -> print file:line, exit 1
  no catalogs?      -> exit 1
  content/<Catalog>.html               # CheckGenerator.compileDoc, same as the IDE
  delete pages of removed catalogs
  toc.xml, contexts.xml                # CheckDocumentationTemplates, PDE layout
  index.html                           # new landing page

Where the pieces live:

 com.avaloq.tools.ddk.check.core/
+├── standalone/CheckDocApplication.java          # the headless application
 ├── generator/
+│   ├── CheckDocumentationTemplates.java         # toc, contexts, index, shared CSS
 │   └── CheckGenerator.java                      # compileDoc restyled, labels and messages escaped
 └── plugin.xml                                   # + docApplication
 com.avaloq.tools.ddk.check.core.test/
+└── CheckDocGenerationTest.java                  # golden files, end-to-end, failure cases
 com.avaloq.tools.ddk.check.test.runtime/
 ├── pom.xml                                      # + opt-in generateCheckDocs profile
 └── docs/                                        # regenerated with the profile
+docs/check-doc-generation.md                     # consumer guide

Verified end to end with a throwaway consumer project (a bare Tycho bundle with one .check file and the guide's profile), against the locally built p2 site: the pages are written, and a syntax error fails the build without writing anything.

A consuming project adds the profile to its bundle and runs mvn -PgenerateCheckDocs -DskipTests package. The guide lists the p2 sites the eclipse-run step needs and shows how to register the Help files. To regenerate this repository's snapshot:

./mvnw -f ddk-parent/pom.xml -pl :ddk-target,:com.avaloq.tools.ddk.check.test.runtime,:ddk-repository -am -PgenerateCheckDocs -DskipTests clean package

🤖 Generated with Claude Code