You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@creadur.apache.org by "lucas theisen (JIRA)" <ji...@apache.org> on 2013/11/28 17:32:37 UTC
[jira] [Updated] (RAT-157) Use the *ignore file for the SCM to
determine excludes
[ https://issues.apache.org/jira/browse/RAT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lucas theisen updated RAT-157:
------------------------------
Description: As I understand it, RAT is used to ensure the LICENSE text is in all source files. Anything ignored by SCM is not technically a source file. These other files are usually specific to the developer environment. And the developer will already be adding such files to their own *SCMignore*. Perhaps a pluggable ingore mechanism that could have an implementation per SCM and would know how to parse that ignore and translate filter out all the files it specifies. Perhaps this could be an option to the the rat config `useGitIgnore` or something. What do you think? (was: As I understand it, RAT is used to ensure the LICENSE text is in all source files. Anything ignored by SCM is not technically a source file. These other files are usually specific to the developer environment. And the developer will already be adding such files to their own `SCMignore`. Perhaps a pluggable ingore mechanism that could have an implementation per SCM and would know how to parse that ignore and translate filter out all the files it specifies. Perhaps this could be an option to the the rat config `useGitIgnore` or something. What do you think?)
> Use the *ignore file for the SCM to determine excludes
> ------------------------------------------------------
>
> Key: RAT-157
> URL: https://issues.apache.org/jira/browse/RAT-157
> Project: Apache Rat
> Issue Type: New Feature
> Reporter: lucas theisen
> Priority: Minor
>
> As I understand it, RAT is used to ensure the LICENSE text is in all source files. Anything ignored by SCM is not technically a source file. These other files are usually specific to the developer environment. And the developer will already be adding such files to their own *SCMignore*. Perhaps a pluggable ingore mechanism that could have an implementation per SCM and would know how to parse that ignore and translate filter out all the files it specifies. Perhaps this could be an option to the the rat config `useGitIgnore` or something. What do you think?
--
This message was sent by Atlassian JIRA
(v6.1#6144)