[
https://issues.apache.org/jira/browse/TIKA-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371458#comment-14371458
]
Ken Krugler commented on TIKA-1581:
-----------------------------------
I heard back from Geert - he says:
bq. It's been ages I look or did anything with that project. However, quickly
scanned through it does indeed seem that it has classes from PCJ that are only
LGPL licensed. If you rip out those classes and replace them with some other
collections, all the rest seems CDDL/LGPL dual licensed. I'm sorry I can't
delve deeper into that, haven't touch that code for almost 10 years.
The "primitive collections for Java" (PCJ) code is indeed LGPL, which creates
new issues (e.g.
https://github.com/codelibs/jhighlight/blob/057d964561562fe4166d1c01e1f3553206693443/src/main/java/com/uwyn/jhighlight/pcj/set/AbstractCharSet.java)
> jhighlight license concerns
> ---------------------------
>
> Key: TIKA-1581
> URL: https://issues.apache.org/jira/browse/TIKA-1581
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.7
> Reporter: Karl Wright
>
> jhighlight jar is a Tika dependency. The Lucene team discovered that, while
> it claims to be a CDDL/LGPL dual-license, some of its functionality is LGPL
> only:
> {code}
> Solr's contrib/extraction contains jhighlight-1.0.jar which declares itself
> as dual CDDL or LGPL license. However, some of its classes are distributed
> only under LGPL, e.g.
> com.uwyn.jhighlight.highlighter.
> CppHighlighter.java
> GroovyHighlighter.java
> JavaHighlighter.java
> XmlHighlighter.java
> I downloaded the sources from Maven
> (http://search.maven.org/remotecontent?filepath=com/uwyn/jhighlight/1.0/jhighlight-1.0-sources.jar)
> to confirm that, and also found this SVN repo:
> http://svn.rifers.org/jhighlight/tags/release-1.0, though the project's
> website seems to not exist anymore (https://jhighlight.dev.java.net/).
> I didn't find any direct usage of it in our code, so I guess it's probably
> needed by a 3rd party dependency, such as Tika. Therefore if we e.g. omit it,
> things will compile, but may fail at runtime.
> {code}
> Is it possible to remove this dependency for future releases, or allow only
> optional inclusion of this package? It is of concern to the ManifoldCF
> project because we distribute a binary package that includes Tika and its
> required dependencies, which currently includes jHighlight.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
