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

Jukka Zitting commented on TIKA-888:
------------------------------------

bq. The question is: The parser is still listed in META-INF, so when a Java 5 
users tries to parse a NetCDF file, he gets a ClassNotFound by the NetCDF 
parser. Whats the best way to handle that?

By default Tika should just ignore the {{ClassNotFoundException}} in such a 
case, so there should be no harm in having the NetCDF parser included in the 
services file.

If that doesn't work (i.e. you get an error when starting Tika), we should fix 
Tika to catch the problem.
                
> NetCDF parser uses Java 6 JAR file and test/compilation fails with Java 1.5, 
> although TIKA is Java 1.5
> ------------------------------------------------------------------------------------------------------
>
>                 Key: TIKA-888
>                 URL: https://issues.apache.org/jira/browse/TIKA-888
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 1.0
>            Reporter: Uwe Schindler
>            Assignee: Chris A. Mattmann
>
> Lucene/Solr developers ran this tool before releasing Lucene/Solr 3.6 (Solr 
> 3.6 is still required to run on Java 1.5, see SOLR-3295): 
> http://code.google.com/p/versioncheck/
> {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}
> TIKA should use a 1.5 version of this class and especially do some Java 5 
> tests before releasing (as it's build dependencies says, it's minimum Java5). 
> I tried to compile and run TIKA tests with Java 1.5 -> crash (Invalid class 
> file format).

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

        

Reply via email to