I know this is off topic, but have the devs looked at / considered using this maven plugin before?
http://mathieu.carbou.free.fr/p/maven-license-plugin/plugin-info.html I use it on all of my projects - it will automatically add the license to files that don't have it / update ones that have an out-of-date / wrong license header. You can also configure it into the "test" target in maven so that the build will fail if files don't have the license. Here's an example of a small wicketstuff project I had started that uses it in the pom: https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-client-and-server-validation/pom.xml -- Jeremy Thomerson http://www.wickettraining.com On Mon, Nov 3, 2008 at 3:02 PM, Frank Bille <[EMAIL PROTECTED]> wrote: > On Mon, Nov 3, 2008 at 9:50 PM, Timo Rantalaiho <[EMAIL PROTECTED] > >wrote: > > > > RAT log: > > > > > > http://people.apache.org/~frankbille/releases/apache-wicket-1.4-rc1/apache-wicket-1.4-rc1.rat.log > < > http://people.apache.org/%7Efrankbille/releases/apache-wicket-1.4-rc1/apache-wicket-1.4-rc1.rat.log<http://people.apache.org/~frankbille/releases/apache-wicket-1.4-rc1/apache-wicket-1.4-rc1.rat.log> > > > > > > I'm still a bit unsure of what this is supposed to contain > > exactly. 820 Unknown Licenses, but there's a lot of jars, > > DTD, velocity templates, example HTMLs, archetype files... > > It's a bit much to really go through these :) > > ApacheLicenseHeaderTestCase feels quite a lot more convenient > > even if it's not as exhaustive. > > > > You are right, it can be a bit difficult to know what to look for and how > this compares with our license header test. > The unit test covers the projects in svn. We have taken a position on all > the files there that doesn't have a license header, or have a different > one. > This is normally because it's either a test file, examples or archetype. > The RAT file shows what our distribution contains of files. This is > important because we might introduce new files in the distribution (f.ex. > generated). At some point it would be useful to create a more integrated > report with our own unit tests or something. > > Frank >
