tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Palsulich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-1581) jhighlight license concerns
Date Sat, 28 Mar 2015 14:14:53 GMT

    [ https://issues.apache.org/jira/browse/TIKA-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385324#comment-14385324

Tyler Palsulich commented on TIKA-1581:

Is this fully resolved? Or, do we need an updated version of JHighlight in Central?

Once this is done, we'll need to release another version of Tika so downstream libraries don't
have the transitive license issue. Correct me if I'm wrong.

> 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
>             Fix For: 1.8
> 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

This message was sent by Atlassian JIRA

View raw message