From 897cbc2181b0893ee41fe19c86fcf9084ba6c7e1 Mon Sep 17 00:00:00 2001 From: Sylwester Lachiewicz Date: Mon, 10 Aug 2026 01:54:33 +0200 Subject: [PATCH 1/2] Rename the FAQ ahead of converting it Git records a rename plus a rewrite in one commit as a delete and an add, which stops 'git log --follow'. Splitting the rename out keeps the history. Please merge or rebase rather than squash. Generated-by: Claude Opus 5 (1M context) --- src/site/{fml/faq.fml => markdown/faq.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename src/site/{fml/faq.fml => markdown/faq.md} (100%) diff --git a/src/site/fml/faq.fml b/src/site/markdown/faq.md similarity index 100% rename from src/site/fml/faq.fml rename to src/site/markdown/faq.md From d5b0ca80a7a3ec82a0918aed8107f38b57082ac8 Mon Sep 17 00:00:00 2001 From: Sylwester Lachiewicz Date: Mon, 10 Aug 2026 01:57:43 +0200 Subject: [PATCH 2/2] Convert the FAQ from FML to Markdown doxia-converter cannot target FML usefully - the questions come out as link-reference syntax rather than headings, the [top] back-links become links to a nonexistent 'top' page, and the contents links lose their # anchors. The page is written out by hand instead. Explicit anchors keep the existing deep links working. All 1 still resolve. Where an id was not a valid XML name, Doxia rewrote it at render time via DoxiaUtils.encodeId; the anchors written here reproduce that rendered form, not the raw attribute. Verified by building the site before and after and comparing the set of anchors the generated faq.html actually serves: every anchor present before is still present after, the is byte-identical, and every link target on the page is unchanged. site.xml needs no edit: src/site/fml/faq.fml and src/site/markdown/faq.md both render to faq.html. FML generates a [top] back-link after each answer; those are dropped rather than hand-written, which is the only rendering loss. The anchors are written rather than : maven-site-plugin 3.21.0 silently drops a name attribute from inline HTML, leaving the build green and every deep link broken. The id form works on every version and is the correct HTML5 spelling. Generated-by: Claude Opus 5 (1M context) --- src/site/markdown/faq.md | 43 ++++++++++++++++++++-------------------- 1 file changed, 21 insertions(+), 22 deletions(-) diff --git a/src/site/markdown/faq.md b/src/site/markdown/faq.md index 469a9f3d9..955c38aec 100644 --- a/src/site/markdown/faq.md +++ b/src/site/markdown/faq.md @@ -1,4 +1,6 @@ - +--- +title: Frequently Asked Questions +--- - - - - How do I add my generated sources to the compile path of Maven, when using Modello? - -

Modello generates the sources in the generate-sources phase and automatically adds the - source directory for compilation in Maven. So you don't have to copy the generated sources. -

-

You have to declare the Modello Maven Plugin - in the build of your project for source generation (in that way the sources are generated each time). -

-

For more information about Modello, please visit the - Modello website. -

- - - - + + +# Frequently Asked Questions + +1. [How do I add my generated sources to the compile path of Maven, when using Modello?](#how-to-add-generated-sources) + + + +### How do I add my generated sources to the compile path of Maven, when using Modello? + +Modello generates the sources in the generate-sources phase and automatically adds the source directory for +compilation in Maven. So you don't have to copy the generated sources. + +You have to declare the [Modello Maven Plugin](https://codehaus-plexus.github.io/modello/modello-maven-plugin/) +in the build of your project for source generation (in that way the sources are generated each time). + +For more information about Modello, please visit the +[Modello website](https://codehaus-plexus.github.io/modello/).