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

Philipp Ottlinger commented on RAT-240:
---------------------------------------

Hi guys, [~utzig][~janc]
I'm afraid I'm still unable to understand your problems.

I've clone your repository
✔ ~/workspace/mynewt-core [master|…1] 
and added a run.sh which yields the following output:

$ ./run.sh 
Ignored 111 lines in your exclusion files as comments or empty lines.

*****************************************************
Summary
-------
Generated at: 2017-11-23T23:40:35+01:00

Notes: 4
Binaries: 0
Archives: 0
Standards: 1830

Apache Licensed: 1813
Generated Documents: 0

JavaDocs are generated, thus a license header is optional.
Generated files do not require license headers.

1 Unknown Licenses

*****************************************************

Files with unapproved licenses:

  ./run.sh

*****************************************************

.....

My run.sh is:

$ cat run.sh 
#!/bin/bash
/home/me/jdk1.8.0_152/bin/java -jar 
../rat-trunk/apache-rat/target/apache-rat-0.13-SNAPSHOT.jar -E .rat-excludes -d 
. | more

I've checked you rat and build it a while ago, thus the reference.

As the build goes through successfully I don't know what I miss here.





> CLI: RAT excludes file does not allow to set a full path
> --------------------------------------------------------
>
>                 Key: RAT-240
>                 URL: https://issues.apache.org/jira/browse/RAT-240
>             Project: Apache Rat
>          Issue Type: Bug
>          Components: cli, scan
>    Affects Versions: 0.12
>            Reporter: Szymon Janc
>            Assignee: Philipp Ottlinger
>             Fix For: 0.12
>
>         Attachments: rat.txt
>
>
> it is not possible to exclude file (or folder) by providing full path
> eg
> foo/foo2/main.c
> bar/bar2/main.c
> it is not possible to match only one of those file from project top directory 
> .rat-excludes file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to