[
https://issues.apache.org/jira/browse/SOLR-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242270#comment-13242270
]
Uwe Schindler commented on SOLR-3295:
-------------------------------------
If you do this, the problem does not get better. A user who feeds a nc file to
Solr Extraction handler will get ClassNotFoundException, thats identical
problem like an invalid class format (we have now). The only difference is,
that it would work if he uses Java 6 (what most users do). The problem here is
more consistency.
If we want to fix it correct, we have to add some configuration class file to
contrib/extraction, listing all supported parsers, so Solr will not chosse one
thats not there.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
