[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887811#comment-17887811
]
Michael Osipov edited comment on DOXIASITETOOLS-355 at 10/9/24 8:19 AM:
------------------------------------------------------------------------
Does {code}**/_*/{code} not work? If it does not, we need to take a look at the
unterlying exluding mechanism. It is part of Plexus Utils. There it needs to be
fixed first.
was (Author: michael-o):
Does {code}**/_*/{code} not work?
> Support file filtering in Doxia ParserModule
> --------------------------------------------
>
> Key: DOXIASITETOOLS-355
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-355
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Integration Tools, Site renderer
> Affects Versions: 2.0.0
> Reporter: Abel Salgado Romero
> Priority: Minor
>
> When defining a module one can define the file extensions to process.
> However, more complex scenarios require more than a extension.
> For example, in the [Asciidoctor
> module|https://github.com/asciidoctor/asciidoctor-maven-plugin/issues] it's
> possible to have "hidden" (use _ prefix) files that are not to be converted
> directly, instead these are to be included in others.
> My first though is to be able to pass a `FilenameFilter` in the constructor.
> The filter would be matched against files that comply with the file
> extensions to confirm whether these should be processed or not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
