On Mon, Feb 23, 2009 at 3:09 PM, Simon Laws <simonsl...@googlemail.com>wrote:
> There are a couple of things, re. our legal files, that could be more > automatic during the release process > > - check that all of our released artifacts have LICENSE/NOTICE files > (sounds like a job for the IANAL plugin) > - check that what's in out legals files is accurate > > So I want to discuss here is whether there are tools that can do this for > us (either with the structure of the LICENSE/NOTICE files at it stands or > with a new structure). > > We currently have shell scripts that will check that our main LICENSE file > has entries for all the 3rd party jars in the lib dir and that there are no > 3rd party jars that don't appear in the LICENSE file. We could instigate a > itest/distribution test to check this. However are there any existing tools > that could do a more thorough job for us for free? > > Going further could we check that each released artifact has > NOTICES/LICENSES that match the licenses/notices that appear in the source > for that artifact. > > I remember looking at a project a while back that used a plugin to > construct LICENSE/NOTICE files based on meta data on disc. I seem to > remember it was CxF but can't put my finger on the right pom. I've just come > across another project that created a bespoke script to do this for NOTICE > files (Sling). I'm asking here before starting to trawl through other > projects/Google in case someone has looked into this stuff recently and > knows the current best practice. > > Simon > > > +1 to doing that. But I don't know how either sorry so would just have to trawl through other projects/Google too. ...ant
