I am a lawyer, but this is not legal advice. As a general rule, if the code is included in your project, you're bound by the license under which that code is made available. That includes dependencies.
There may be some exceptions depending on the license(s) and how they all plug together (as a crude example, the MIT license attribution requirement might already be satisfied by a downstream bundler - upstream from you - including the necessary language). Personally, I'd conduct a review of each component if license compliance is important to you (e.g., if you're going to release a commercial product incorporating the code). Sent from my iPad > On Jul 13, 2015, at 1:39 AM, James Baker <[email protected]> wrote: > > Hi, > > Apache Tika is licensed under the ASL2 license, but a number of it's > dependencies aren't - for example Java UnRar is licensed under the UnRar > license. > > Can someone explain to me how this works? If I am looking at releasing my own > software that is dependent on Tika, can I release it under ASL2 or do I also > need to take into account the licenses of the sub-dependencies? > > Thanks, > James
