[ 
https://issues.apache.org/jira/browse/DOXIASITETOOLS-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803924#comment-17803924
 ] 

ASF GitHub Bot commented on DOXIASITETOOLS-324:
-----------------------------------------------

kwin commented on code in PR #126:
URL: 
https://github.com/apache/maven-doxia-sitetools/pull/126#discussion_r1443970810


##########
doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/SiteRenderingContext.java:
##########
@@ -388,4 +391,20 @@ public File getRootDirectory() {
     public void setRootDirectory(File rootDirectory) {
         this.rootDirectory = rootDirectory;
     }
+
+    /**
+     *
+     * @return the retriever for parser configurations (only relevant for 
Doxia sources)
+     * @since 2.0.0
+     */
+    public ParserConfigurationRetriever getParserConfigurationRetriever() {
+        if (parserConfigurationRetriever == null) {

Review Comment:
   because this is not supposed to return null ever (will clarify in the 
javadoc).





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

Reply via email to