Thanks Sean and Ted, I now understand the policy to deal with the license
validations, will follow that. Thanks,Guang
On Tuesday, October 4, 2016 3:15 PM, Sean Busbey <[email protected]>
wrote:
1) CDDL + GPLv2 allows you to pick a license. as an ASF project we
pick CDDL. You should update the supplemental info to properly
document the use of CDDL (including the version).
2) You should update the supplemental info file to refer to the correct name.
You should also make sure there are no additional changes needed to
LICENSE or NOTICE files for the change in dependencies beyond what the
automatic tooling does.
On Tue, Oct 4, 2016 at 2:40 PM, Guang Yang <[email protected]> wrote:
> Hello,
> While working on the Jetty 9 upgrade patch, after polling in several new
> artifacts, the build failed due to the license validation, for example:
> 1. It pulled in the javax.annotation whose license is 'CDDL + GPLv2 with
> classpath exception' which failed our whitelist check since once 'CDDL' is
> found, it tries to find '1.1' or '1.0' but failed to find those sub strings.
>
> 2. Another one failed the validation is javax.validation, whose license is
> 'Apache Software License, Version 2.0', whereas in our whitelist, it is
> 'Apache License, Version 2.0' (note there is no 'Software').
>
> I would like to ask what is the recommendation to deal with this type of
> mismatch?
>
> Thanks,
> Guang
--
busbey
