Now that Lucene 1.4 looks underway, there seems to be a bit of a
dilemma. Solr 1.3 release seems to be planned a bit ahead of Lucene 1.4.
Release just before a Lucene release, or wait and get a nice even Lucene
1.4 release?
Even if there is a wait for 1.4, if the past is any clue, solr 1.3 will
quickly be outdated with 1.4.1 anyway.
- Mark
Lars Kotthoff (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SOLR-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623522#action_12623522 ]
Lars Kotthoff commented on SOLR-697:
------------------------------------
Can we update the jars rather sooner than later (i.e. now) so that people get a
chance to test everything before the 1.3 release?
Update Lucene jar before 1.3 release (was: Lucene TimeLimitCollector)
---------------------------------------------------------------------
Key: SOLR-697
URL: https://issues.apache.org/jira/browse/SOLR-697
Project: Solr
Issue Type: Bug
Components: update
Affects Versions: 1.3
Reporter: Wayne Graham
Fix For: 1.3
When instantiating a SolrCore using the Solr API, a Lucene exception is thrown
{{
org.apache.solr.core.SolrResourceLoader createClassLoader
INFO: Reusing parent classloader
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/lucene/search/TimeLimitedCollector$TimeExceededException
at org.apache.solr.core.SolrConfig.<init>(SolrConfig.java:132)
at org.apache.solr.core.SolrConfig.<init>(SolrConfig.java:101)
...
}}
Updating the lucene-core-2.4-dev.jar that is included in the nightly to a more
current snapshot resolves the problem (tested with Lucene r685576).
