Going a bit down the rabbit hole, we may need to look at the licensing of as3crypto, which is what as3httpclientlib depends on for SSL/TLS. It looks like the library itself is BSD based, but it depends on other granted licenses. https://github.com/BenV/as3crypto_patched/blob/master/LICENSE.txt
Any thoughts on that portion? Luckily it's not export controlled (there are some versions of as3crypto that are export controlled...) -Nick On Tue, May 26, 2015 at 5:44 PM, Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > > My understanding on how to bring in code we don't own, but utilize is via > > the ANT scripts. Is there a different way? > > Yes you can bundled it into the source. BSD is one of the simplest cases > being a permissive licence. [1] The code can live in version control if it > clearly marked and it’s existing headers left alone and the BSD license > file included. > > IMO Having the installer rely on 3rd party source code is preferable to > have it rely on a 3rd party binary, particularly when the source is > available under a permissive license. > > Justin > > 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps
