slachiewicz opened a new issue, #1101: URL: https://github.com/apache/maven-doxia/issues/1101
FML has been a source-only format since Doxia 2.0.0, and its `title`, `question` and `answer` bodies are already parsed as XDoc ([DOXIA-765](https://issues.apache.org/jira/browse/DOXIA-765)). An FAQ page written in Markdown or XDoc loses nothing, and [doxia-converter](https://maven.apache.org/doxia/doxia-tools/doxia-converter/) accepts FML as an input format, so existing pages have a mechanical migration path. Maven's own documentation has already moved: on the default branches of apache/maven-* the only remaining `.fml` files are test fixtures (doxia-test-docs, maven-site-plugin ITs) and the `maven-archetype-site` template. Outside Maven the format is still in use (`filename:faq.fml org:apache` finds 59 files across commons-*, james, myfaces, ranger and others), which is why this is a deprecation, not a removal. Proposal, following the DOXIA-621 → DOXIA-630 precedent: 1. **2.2.0:** mark `doxia-module-fml` deprecated: `@Deprecated` on its public classes, a deprecation notice on the module site, and a `WARN` per parsed FML document pointing at this issue. 2. **Next major:** remove the module from doxia, doxia-sitetools and maven-site-plugin. doxia-converter keeps FML as an input format so the migration path survives the removal. Follow-ups in other repos: a deprecation banner on [references/fml-format.html](https://maven.apache.org/doxia/references/fml-format.html) (maven-doxia-site) and switching the `maven-archetype-site` FAQ template to Markdown. Origin: DOXIA-765 comment thread, where this was asked to be tracked separately. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
