Some of the examples of this are to have the external
LGPL library at Github (I remember Jukka Zitting did
a MS TNEF parser that did this) and then just having it
as a separate plugin. I don’t think we should add potential
“surprises” for people expecting Tika to not have any
core deps on LGPL. Nick also has the Vorbis (misspelling
that I know) on Github, not sure if it’s for the same
reason.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: [email protected]
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++






-----Original Message-----
From: <Allison>, "Timothy B." <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Friday, February 13, 2015 at 4:16 AM
To: "[email protected]" <[email protected]>
Subject: Parser that includes LGPL as "provided"?

>All,
>  After I dig myself out of several other issues that I'd like to tackle,
>I'd like to add a parser for MSAccess files.  There's a pure java LGPL
>library, Jackcess, available on maven, and it appears to be quite active.
>  I know we have a list of third party parsers, but I'm wondering if we
>could write a Tika parser that uses Jackcess but sets it as "provided" in
>the pom.  This seems to me to be equivalent to our current "excludes"
>statements for some other LGPL files.
>   Users would be responsible for grabbing the jar and putting it on
>their classpath, and our parser would check to see if it was available in
>the classpath before parsing or even admitting that it could handle an
>MSAccess file.
>  Is this ok?  Or would we have to offer the Tika parser as a purely
>third party option, i.e. hang it on github?
>
>    Thank you.
>
>         Best,
>
>             Tim
>

Reply via email to