[
https://issues.apache.org/jira/browse/RAT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025172#comment-17025172
]
Benjamin Young commented on RAT-262:
------------------------------------
Seems like that should work for now. JSON files--especially in JavaScript-based
projects--often hold license related data that RAT would probably care about.
That's especially true for projects using NPM:
https://docs.npmjs.com/files/package.json#license But it's also true for PHP
projects using Composer: https://getcomposer.org/doc/04-schema.md#license
So, eventually, it'd be better to have these JSON files parsed for the data
they provide.
This certainly avoids the JSON-can't-have-comments issue reported here, though,
so +1. :)
> Ignore all `.json` files
> ------------------------
>
> Key: RAT-262
> URL: https://issues.apache.org/jira/browse/RAT-262
> Project: Apache Rat
> Issue Type: New Feature
> Components: scan
> Affects Versions: 0.13
> Reporter: Benjamin Young
> Assignee: Philipp Ottlinger
> Priority: Minor
> Labels: core
> Fix For: 0.14
>
>
> JSON lacks comments, so they are not able to have a license header to
> scan/find. Consequently, all JSON files aren't worth scanning.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
