On Tue, 14 Jul 2015, Chris Harshman wrote:
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).
While Apache tries to ensure the software it produces is "commercially
friendly", this is good advice, especially if you're new to including open
source in your project.
The ASF has rules on what kinds of licenses dependencies are allowed to
have, to try to ensure that you can use ASF projects under basically the
terms of the Apache License v2, without having a dependency "surprise" you
by forcing the whole lot under different conditions. You can read about
this, and the allowed + forbidden licenses here:
http://www.apache.org/legal/resolved.html
If you want to find the background to any of those decisions, you'd need
to check the ASF legal jira, and the ASF legal-discuss list
If we've done it right, you should be fine to use Apache Tika in your
commercial product, modulo the usual restrictions in the license on
attribution, notices, trademarks, no support/warranty etc, for Tika and
the dependencies. That said, you didn't pay for Tika, and you didn't pay
for this advice, so depending on your experience + use-case you may wish
to check it formally!
Nick
