Yeah, they advertise RAT as heuristical, and we are abusing it to
detect missing copyright headers for the most part (typically, someone
forgets the apache license one). So from time to time we will have to
update the heuristics for licenses that it cannot recognize.
On Fri, Jan 30, 2015 at 3:25
Thanks Robert,
I found it confusing because the config for Solr was inside Lucene, not
where I would have expected it, but glad to know I was in the right
place.
What you said was exactly what I needed. The Rat output shows some JS
libraries as not passing (e.g. angularJS) so I just need to add
You are correct the main logic is in lucene/common-build, I dont see
why you think that is confusing. Do you think the license verification
logic shoudl be duplicated twice in the build system? anyway there are
some hooks like $rat.excludes for a module to override with.
Can you explain a little
As a part of SOLR5507, I'm trying to get RAT to pass. I've dug around,
and got very confused. It seems that the config for Solr RAT is in
lucene/common-build.xml, which doesn't make much sense, and there are
licenses I can't find in there.
Can someone explain to me how I tell RAT that a specific
