German,
otherwise you can download the lib during the build process. In this
case it won't be a part of source release.

--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://dataved.ru/
+7 916 562 8095


On Tue, Aug 7, 2012 at 2:03 PM, [email protected]
<[email protected]> wrote:
> RAT is a tool to check the sources of files that we produce, not files
> that we do not maintain and are derivate work licensed udner different
> terms.
> You could exclude those files from the RAT test from my point of view.
>
> The more important thing will be to correctly mention those
> dependencies in the LICENSE file. Then it should fine.
>
> Sebastian
>
> 2012/8/7 German Grekhov <[email protected]>:
>> Hello.
>>
>> I try to set up Jenkins build for Teambox plugin. And first of all, it was
>> needed to make the code suitable for releasing, so I have checked that all
>> files contains license headers.
>>
>> But I can not automate this process. Teambox plugin uses 3rd party library
>> to make OAuth 2.0 requests. And the library is under MIT license. When I
>> tried to run Apache Rat for the plugin I found that it does not recognize
>> MIT license headers in library's files.
>>
>> I have found that it was a bug in the Apache Rat:
>> https://issues.apache.org/jira/browse/RAT-49 (currently jira is broken)
>>
>> And it has already been fixed, but the Apache Rat 0.9 version was not
>> released yet.
>>
>> Do you have any ideas about what should we do?
>>
>> Thanks and best regards,
>> German Grekhov.
>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> [email protected]

Reply via email to