I will probably submit a patch to RAT at some point for this, but wanted to prove it out here first as we have an immediate need and I don't want to wait for a RAT release nor do I have the time to learn the RAT code at this point. Others are welcome to port it.
-Grant On Mar 17, 2011, at 1:58 AM, Mark Miller wrote: > We do use Apache RAT and it does not do these kinds of license checks. > > On Mar 16, 2011, at 9:19 PM, Mattmann, Chris A (388J) wrote: > >> Have you guys thought about using Apache RAT [1]? >> >> It's not perfect but it implements a lot of license checks, and as far as I >> know, integrates nicely into Ant and Maven. >> >> Cheers, >> Chris >> >> [1] http://incubator.apache.org/rat/ >> >> On Mar 16, 2011, at 5:54 PM, Robert Muir wrote: >> >>> On Wed, Mar 16, 2011 at 3:57 PM, Grant Ingersoll <[email protected]> >>> wrote: >>>> As Robert can no doubt attest, we often scramble to make sure i's are >>>> dotted and t's are crossed when it comes to filling out LICENSE.txt and >>>> NOTICE.txt right before releases, thereby burdening the RM with way too >>>> much work in validating what dependency has which license. Thus, we've >>>> been working to resolve this. >>>> >>>> In prep for the landing of LUCENE-2952 and to make life easier on release >>>> managers going forward, we've adopted the following conventions for >>>> dealing with licenses: >>>> >>>> 1. For every dependency (i.e. jar file), there needs to be a corresponding >>>> file-LICENSE-<LICENSE_TYPE>.txt file, as in: foo-2.3.1.jar has the >>>> corresponding foo-LICENSE-BSD.txt file (assuming foo is BSD licensed) in >>>> the same directory as the jar file. >>>> >>>> 2. _IF_ the license requires a NOTICE entry, then there must be a file of >>>> the name file-NOTICE.txt, as in foo-NOTICE.txt. >>>> >>>> Failing to meet either one will break the build once L-2952 is committed >>>> (which should be soon for trunk and will be backported to 3.2). >>>> >>>> Consider yourself notified. >>> >>> +1 >>> >>> I think we can all agree, we want our licensing to be "rock-solid" and >>> we should strive to raise the standards here for our project. Its >>> actually more important than if our code even compiles. >>> >>> Automated checks go a long way, thank you Grant for working on this, >>> because we have a lot of third-party dependencies and its difficult to >>> verify that everything is in proper order. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Chris Mattmann, Ph.D. >> Senior Computer Scientist >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> Office: 171-266B, Mailstop: 171-246 >> Email: [email protected] >> WWW: http://sunset.usc.edu/~mattmann/ >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Adjunct Assistant Professor, Computer Science Department >> University of Southern California, Los Angeles, CA 90089 USA >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > - Mark Miller > lucidimagination.com > > Lucene/Solr User Conference > May 25-26, San Francisco > www.lucenerevolution.org > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -------------------------- Grant Ingersoll http://www.lucidimagination.com/ Search the Lucene ecosystem docs using Solr/Lucene: http://www.lucidimagination.com/search --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
