I'm not an expert on this area, but do a search of the codebase for files called thirdpartylibs.xml. These are used by various components do define any libraries they include, along with their licenses. They're also used by tools like grunt to exclude these libraries from automated checks. Adding one of these files to your plugin and listing your web service code in it will make it clear that you're including separate code under the Apache v2 license.
Re: Licensing/code implications of distributing external file chooser with plugin code
by Mark Johnson -
Number of replies: 0