The final step of this project is to have the generation happen in mvn site phase. As of now, we use a @BeforeAll method in XdocsPagesTest to generate Xdocs. We use a custom parser, custom sink, and custom sink factory. The reason we have them is because we want to isolate macro execution from parsing the rest of the file to HTML. Once the whole repository is converted to templates and we are certain the generation is good, those 3 modules will be removed. The default XdocParser in mvn site phase will execute the macros and parse to HTML for us.

please beware of #13770 fix that introduced extra overrides to doxia files that might cause extra complexity in this issue. Completing #13426 means we will be removing the classes we copied and hacked from Doxia (XdocsTemplateSink) which is documented at

. When completing #13426 and removing the class, we need to re-open #13770 and find a permanent fix unless doxia resolves our internal issues at https://issues.apache.org/jira/browse/DOXIA-707 .

Interesting note at https://issues.apache.org/jira/browse/DOXIA-707

Since you want to migrate to a Maven Site Plugin approach, you don't need to generate XDoc at all. kwin, has just migrated Maven Plugin Tools off XDoc to an abstract sink provided by Maven Reporting Impl.

Move xdoc doxia parsers and macroses to separate project in contribution repo
detected at #13357 (comment)
we should move all out, to note pollute in main repo. We should not export such classes to final jar we release.