slachiewicz commented on issue #736:
URL: 
https://github.com/apache/maven-doxia-sitetools/issues/736#issuecomment-6864577597

   I revised the proposal in the description after looking at it against Maven 
3.9, 3.10 and 4 and the answer in apache/maven#13827. Three things changed:
   
   - The context is an argument of a new `Parser.parse(Reader, Sink, 
ParserContext)` default method in doxia-core, not a setter. Parsers are shared 
instances, and a parser implementing an opt-in Sitetools interface fails to 
load with an older Sitetools, so the fallback would never run.
   - The context exposes JDK types only: no `Xpp3Dom`, no attributes map, and a 
relative output name plus an optional output directory instead of an absolute 
output file. The same parser then works on all three Maven lines.
   - Parser options are split out as an open question. This replaces my earlier 
preference for `<custom>`, which is also an `Xpp3Dom`.
   


-- 
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]

Reply via email to