You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Shai Erera (JIRA)" <ji...@apache.org> on 2015/03/20 12:47:38 UTC

[jira] [Commented] (TIKA-1581) jhighlight license concerns

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

Shai Erera commented on TIKA-1581:
----------------------------------

Note that in jhighlight trunk these files are distributed under both licenses: http://svn.rifers.org/jhighlight/trunk/. However, all files under http://svn.rifers.org/jhighlight/trunk/src/com/uwyn/jhighlight/pcj/* seem to be LGPL only too. They are distributed as part of the .jar as well.



> 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)