[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805506#comment-17805506 ]
ASF GitHub Bot commented on DOXIASITETOOLS-324: ----------------------------------------------- michael-o commented on PR #126: URL: https://github.com/apache/maven-doxia-sitetools/pull/126#issuecomment-1886888874 > > We always operate on parser modules consistently, thus I would expect that a parser config applies on a per-module basis. > > You are probably right, a config mapping per id seems sufficient here. Yes > > The parser config isn't flexible > > Right, but changing it would either require to add something like `Parser.configure(Map<String,String> config)` to Doxia which kind of conflicts with the existing setters or some sophisticated reflection to call the right setter. The tricky part is not to call the right setter method but to convert the parameter to the right type (leveraging the Plexus conversion logic). Which way of implementing this did you have in mind? About this, I need to think, but you are heading for that direction. I need more time. Can you make the first one happen as long as I think about the first one? > Allow configuration of parser (per markup source path pattern) > -------------------------------------------------------------- > > Key: DOXIASITETOOLS-324 > URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-324 > Project: Maven Doxia Sitetools > Issue Type: New Feature > Components: Site renderer > Reporter: Konrad Windszus > Assignee: Konrad Windszus > Priority: Major > Fix For: 2.0.0-M17 > > > Currently the Doxia parsers being used for the Doxia markup sources have a > fix configuration > (https://github.com/apache/maven-doxia-sitetools/blob/dacaa552c1b8e89eed84db0f43b6b0a72be91d0c/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java#L324). > It would be beneficial to allow to dynamically configure the parsers (based > on a matching markup source path pattern) -- This message was sent by Atlassian Jira (v8.20.10#820010)