On Mon, Dec 15, 2008 at 1:42 PM, Gordon Sim <[email protected]> wrote: > Aidan Skinner wrote:
>> We shoud really integrate RAT into our release process. > > Are there defined rules for what must, should, may etc have the license > included? Rat seems not to require it for READMEs or generated files? (I > tried running it for the first time today, so not sure if that assumption > is entirely correct. Generated files don't, text files don't, source code does. > The generated c++ API docs don't contain the license, but the source they > are generated from does. Should they have the license in them? What about > the Makefile.am files (i.e the inputs to automake) which currently don't > have them either? I think the API docs don't need the license as they're generated. I'm not sure about the Makefile.ams but they probably do. The java build files have it, as does python/setup.py. Can't hurt to add them. - Aidan -- Apache Qpid - World Domination through Advanced Message Queueing http://cwiki.apache.org/qpid "Have we anything resembling a plan?" "Mm-hm. Ride till we find them... and kill them all." - The 13th Warrior
