The standard Maven documentation plug, -in does not list html among its supported filetypes, perhaps because it performs some styling or validation or indexing of the documents and didn't have an adequate GTML parser available. (Our use of tidy in the tests is an admittedly ugly kluge.) I could work around that by explicitly moving html files but part of my intent is to have the build be idiomatic Maven and that means using the standard tools where I can, just as it means moving to Maven's directory structures. The cost of making the source html files xhtml compatible was acceptable.
Not planning to change this unless there is significant active opposition. Browsers have no objections to xhtml; It's just slightly more rigorous html with an assumed namespace declaration that html ignores. -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ () Plaintext Ribbon Campaign /\ Stamp out HTML mail! ________________________________ From: vlsi (via GitHub) <g...@apache.org> Sent: Thursday, October 19, 2023 2:13:12 AM To: dev@xalan.apache.org <dev@xalan.apache.org> Subject: Re: [PR] Migrate to Maven-based build [xalan-java] vlsi commented on PR #105: URL: https://github.com/apache/xalan-java/pull/105#issuecomment-1770128120 > Removed html files that had been refactored/edited into being xhtml files under src/site/xhtml Could you please explain/provide a link to "maven prefers xhtml"? I don't use Maven, so I might miss its preferences. As far as I can remember, XHTML was abandoned long ago. I performed a random search, and, they say, XHTML was deprecated in 2012: https://softwareengineering.stackexchange.com/a/149843. What do you think of keeping the document as a regular HTML rather than converting it? Are you sure the updated documents are 100% XHTML? As the build scripts have no validation for XHTML, bugs will appear quite fast, and there will be no benefit from declaring "ok, the document is XHTML". -- 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: dev-unsubscr...@xalan.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org