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 more what the problem is? (maybe just include the output from 'ant rat-sources' that fails) If the problem is that its a test file or something that should not relaly have a license (e.g. its something that an analyzer croaked on before), then that rat.excludes is the way to go, just exclude the file completely. otherwise if the license is not recognized, add a substring that would identify it to that logic, under the correct category. On Thu, Jan 29, 2015 at 8:58 PM, Upayavira <[email protected]> wrote: > 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 license is > acceptable? > > I suspect I'm missing something obvious. > > Many thanks! > > Upayavira > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
