The rat check is now part of build execution and can be activated by this
profile:
mvn clean install -Pbuild.quality
Furthermore I added following excludes where it is not possible or not
necessary to add a license:
<exclude>**/MANIFEST.MF</exclude> // no comment possible
<exclude>.gitignore</exclude> // not possible
<exclude>.git/**</exclude> // not necessary
<exclude>bin/**</exclude> // generated
<exclude>**/*.project</exclude> // generated
<exclude>**/*.classpath</exclude> // generated
<exclude>**/*.json</exclude> // no comment possible (test data)
<exclude>**/*.batch</exclude> // no comment possible (OData
batch, test data)
The rat check seems to be ok now and there are no issues reported.
I am going to setup another build job for quality check that runs at least
once a day.
-- Stephan
On 01.08.13 09:13, "Alan Cabrera" <[email protected]> wrote:
>
>On Jul 26, 2013, at 1:52 AM, Dave Fisher <[email protected]> wrote:
>
>> The most important part of the first release for this podling is make
>>sure that the headers are correct. The ASF has a tool that helps called
>>Apache RAT. It can be found here: http://creadur.apache.org/
>
>Since the project is on Maven one can run:
>
>mvn rat:check
>
>to make sure the project's files are conforming to ASF requirements.
>
>
>Regards,
>Alan
>
