On 13/08/16 19:33, Gale Naylor wrote:
Is there a typical or accepted method for making sure the code (including
dependencies) is licence-clean?
A release :-)
The RAT plugin does some checking (all files have the ASF header), and
greping for phrases for other license is effective.
JS, because you end up shipping it's source, needs checking.
For java dependencies I don't know of a better way that "mvn
dependency:tree" and manual checking.
Andy
On Sat, Aug 13, 2016 at 10:44 AM Andy Seaborne <[email protected]> wrote:
On 12/08/16 12:19, Stian Soiland-Reyes wrote:
It would be ideal to have the Server and Workbench released as well -
but I agree with Ian that should not be a blocker for graduation.
It would be good to make sure the code is licence-clean, including
dependencies.
All the code does not have to have been through a release as far as i
know but repo needs to be "clean" and this would be proof of that.
Andy
