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

Uwe Schindler commented on SOLR-3295:
-------------------------------------

This is a long standing issue in TIKA, so that they provide separate parser 
jars, each with own META-INF, splitting the parsers up in e.g. 
tika-office-parsers, tika-image-parsers, 
tika-horrible-huge-climate-data-parsers, tika-soundfile-parsers,... Then each 
of these JARS would have a limited dependency set.

We should open issue (I will check) and suggest that. It annoys me since month. 
Every TIKA release gets more crazy formats nobody is interested ina nd you only 
get a huge tika-parsers.jar will approx 100 3rd-Party JARS you have no control 
anymore.
                
> Binaries contain 1.6 classes
> ----------------------------
>
>                 Key: SOLR-3295
>                 URL: https://issues.apache.org/jira/browse/SOLR-3295
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Dawid Weiss
>            Assignee: Robert Muir
>            Priority: Minor
>             Fix For: 3.6
>
>         Attachments: output.log
>
>
> I've ran this tool (does the job): http://code.google.com/p/versioncheck/ on 
> the checkout of branch_3x. To my surprise there is a JAR which contains Java 
> 1.6 code:
> {noformat}
> Major.Minor Version : 50.0             JAVA compatibility : Java 1.6 
> platform: 45.3-50.0
> Number of classes : 60
> Classes are : 
> c:\Work\lucene-solr\.\solr\contrib\extraction\lib\netcdf-4.2-min.jar [:] 
> ucar/unidata/geoloc/Bearing.class
> ...
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to