slachiewicz commented on PR #149:
URL:
https://github.com/apache/maven-doxia-converter/pull/149#issuecomment-5234382218
Added a third item in `7a1c2d9`, after a second, independent reproduction of
the `##` failure on
an **xdoc**→Markdown conversion (two `<h2>` lost) alongside the APT case in
#148 (four `<h2>`
lost).
The section already described the mechanism, but left the rule implicit
inside the list of
remedies. It now leads with it — *in a file that keeps its `.vm` suffix,
never write an ATX
heading below level one* — and states what both reproductions have in common:
> A green build is not evidence here, and neither is reading the converted
Markdown — the `##`
> looks correct in the source, because it *is* correct Markdown.
In both cases `mvn site` exited zero, every paragraph of prose was intact,
and the `%{toc}` macro
listing the lost sections rendered as an empty list. That is the argument
for the before/after
comparison at the top of the page being mandatory rather than advisable, so
the new text says so
in those terms.
`mvn site` and `mvn verify` green locally (JDK 21, Maven 3.9.16, macOS); RAT
0 unapproved,
23/23 tests. All nine `<h2>` on the page still render.
--
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]
