No license headers

[GoogleCodeExporter]

Most files in TC appear to have no license headers and no license checking 
plugins are run as part of the Maven build.

Original issue reported on code.google.com by richard.eckart on 15 Jun 2014 at 1:51

[GoogleCodeExporter]

which plugin/goal do you recommend? Maven license:check-file-header?

Original comment by daxenber...@gmail.com on 16 Jun 2014 at 12:53

[GoogleCodeExporter]

For ASL modules rat, for GPL modules the mycila plugin - I'd start with the 
same configuration as Uby has based on auto-activating Maven profiles.

Original comment by richard.eckart on 16 Jun 2014 at 4:06

[GoogleCodeExporter]

This issue was updated by revision r900.

adding rat and mycila plugins.
adding GPL headers.
TODO: add ASL headers.

Original comment by daxenber...@gmail.com on 17 Jun 2014 at 6:22

• Changed state: Started

[GoogleCodeExporter]

I will also activate a profile that checks for the existence of a LICENSE.txt 
file in each folder that has a pom.xml file. The LICENSE.txt will be copied 
into the final JARs that get deployed. If you copied code from elsewhere, 
please make sure to also set up a NOTICE.txt file explaining what third-party 
code you include in the JAR, where you got it from and if possible what its 
copyright is. If the code was originally not under the same license as the 
module, please make sure to append the license of the third-party code to the 
respective LICENSE.txt file.

Original comment by richard.eckart on 18 Jun 2014 at 12:20

[GoogleCodeExporter]

Dammit, why didn't I see this issue before when I was scanning for "license"... 
anyway... fixed in issue 156.

Original comment by richard.eckart on 25 Jun 2014 at 3:04

• Changed state: Fixed