Hi Justin,

so, I invested some time today to address the licensing requirements. I 
currently just did that for the servlets module. If that’s ok, then I’ll apply 
similar changes to the server jar.
Now the build generates a THIRD-PARTY.txt file containing the license names and 
the module names which are included in the archive
Additionally the “license” directory contains the textual versoins (TXT or 
HTML) of the licenses.

Chris


Am 27.09.17, 06:45 schrieb "Justin Mclean" <jus...@classsoftware.com>:

    Hi,
    
    > Chris, while the enhancement to make the war’s 
WEB-INF/classes/META-INF/DEPENDENCIES complete with info for bundled external 
jars is great, I believe the war’s LICENSE still needs to have that info too… 
or more sensibly the LICENSE needs to include a reference to that info.  Don’t 
shoot the messenger! :-)
    
    I've taken a quick look and the war/jar bundles:
    
    BSD licensed D3 3.3.9 [1]
    BSD ;licensed d3-plugins-sankey 
    MIT licensed  d3.legend.js
    MIT licensed jQuery 1.11.2
    MIT licensed jQueryUI 1.11.4
    Apache licensed gson-2.8.0
    Apache licensed metrics-core-3.1.2
    
    All of the MIT and BSD licenses need to be added to license, the Apache 
licensed one can be but are optional.
    
    Metrics includes a NOTICE file [1] and that will effect our NOTICE file. 
i.e. it’s contents will need to be added.
    
    Thanks,
    Justin
    
    1. https://github.com/dropwizard/metrics/blob/4.0-development/NOTICE

Reply via email to