: I know that the product in general is licensed as Apache 2.0, but
unfortunately there are packages
: included in the build that are considered "non-permissive" by my company and
as such, means that
...
: It appears that the vast majority of the licensing issues are within the
contrib directory. I know these
...
: just the Solr and Lucene server distribution (minus demos and contrib). Some
of the packages are
: dual licensed so I am able to deal with that by selecting which we wish to
use, but there are some
: that are either not licensed at all or are only non-permissive (ie: not
Apache, BSD, MIT, etc.) like
: GPL, CDDL, etc.
Can you give a specific example of a dependency that you are seeing used
in contrib that is not (dual) licensed under a "permissive" license?
Every jar Lucene/Solr depends on has a corrisponding file in our
*/licenses directories -- so I'm not sure what you mean by "not licensed
at all" There should most cerntainly not be anything that's licensed as
GPL (w/o a dual license option that's more permissive).
Granted: If you consider CDDL to be problematic then you will certainly
have some problems since the javax.servlet *API* is itself under the
CDDL, so you're kind of going to be out of luck as far as being able to
run Solr ... or any java based app that uses servlets.
Having said all of that....
If your legal department feels (for whatever reasons) that solr-core's
dependencies are "ok", but there are contribs with deps that are "not ok",
then there is an easy solution:
1) download a "src" release
2) run "cd solr/webapp && ant dist"
You'll now have a fully functionaly copy of the solr app you can run, and
only the compile dependencies for the core server & solrj will have been
downloaded to your machine -- nothing in contrib will be built, let alone
have any 3rd party deps downloaded.
-Hoss
http://www.lucidworks.com/
