Why not use a JSON Standard like JSON-P? It’ll be required by other Eclipse Projects like MicroProfile, too 😉 Werner It's probably better to just avoid that library altogether. Our IP Team contacted the author some time ago to get a special license for Eclipse projects to use a specific version, but we don't feel that that license applies to subsequent versions. FWIW, the JSON license is problematic for other consumers (the EF isn't alone in having a problem with it). That you can't keep up-to-date with patches is going to be a long term problem. Have you considered adopting an alternative? This library is already available in bundle form in an old drop of Orbit (I see it in a 2012 build [1]). Can you pull the bundle from there? On Tue, May 16, 2017 at 8:57 AM, Rémi Druilhe <remi.druilhe@xxxxxxxxx> wrote: We are using the JSON library with the following maven coordinate: org.json:json:20140107 Due to its specific license, this dependency can not be validated by the EMO team. The EMO team recommands to use the one provided by the CQ3603. We agreed. However, because this dependency is specific to Eclipse (change of the license for Eclipse), can we integrate its source code direclty into our project as a package in one of the bundles. Thus the library will be mixed with our owns classes. If yes, are we allowed to modify it to avoid refactoring all our source code? Best regards.
_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation
-- Wayne Beaton Director of Open Source Projects The Eclipse Foundation |
