[
https://issues.apache.org/jira/browse/RAT-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028421#comment-14028421
]
Erik Erlandson commented on RAT-161:
------------------------------------
to put it another way, as I understand from the doc (and the code), you can
either:
a) specify path names, in maven config, via <exclude>...</exclude>, but not
regular expressions
b) specify a list of regex via '-E', one per line, which cannot currently span
paths, that is match across directory '/'
c) specify regex on the CL via -'e'
The purpose of this RFE is to allow regular expressions, which *can* span
paths, so one can include patterns like 'path/to/file.ext' and '*.pom' in the
same configuration. This might either be done by extending (a) to include
regex that can match across '/', or enhancing (b) to include such regular
expressions as well. Those are not mutually exclusive.
> Support exclusion of paths: "path/to/file.ext"
> ------------------------------------------------
>
> Key: RAT-161
> URL: https://issues.apache.org/jira/browse/RAT-161
> Project: Apache Rat
> Issue Type: New Feature
> Components: reports
> Reporter: Erik Erlandson
> Priority: Minor
> Fix For: 0.11
>
>
> It would be advantageous to be able to exclude specific files, e.g.
> "path/to/file.ext"
> The current '-E' feature cannot do this, as the filter patterns are only
> applied to individual files as directory tree is traversed, so a filter will
> never see "path/to/file.ext", only "path", "to" and "file.ext"
> See for example: SPARK-1493
--
This message was sent by Atlassian JIRA
(v6.2#6252)
