2.0.4
beta是基于lucene什么版本开发的?我在使用lucene1.4.3时运行出��
�。
java.lang.VerifyError: trying to subclass final class
org/apache/lucene/analysis/Token
应该是继承了final的Tocken引起的?
附加信息:
java.lang.VerifyError: trying to subclass final class
org/apache/lucene/analysis/Token
at
java.lang.ClassLoader.defineClass(Ljava.lang.String;[BIILjava.security.Protectio
nDomain;)Ljava.lang.Class;(Unknown
Source)
at
java.security.SecureClassLoader.defineClass(Ljava.lang.String;[BIILjava.security
.CodeSource;)Ljava.lang.Class;(SecureClassLoader.java:123)
....
at java.lang.ClassLoader.loadClassFromNative(II)Ljava.lang.Class;(Unknown
Source)
at jrockit.vm.RNI.getRunnableCode(I)I(Unknown Source)
at jrockit.vm.RNI.trampoline()V(Unknown Source)
at
net.paoding.analysis.analyzer.impl.MostWordsTokenCollector.collect(Ljava.lang.St
ring;II)V(MostWordsTokenCollector.java:???)
at
net.paoding.analysis.analyzer.PaodingTokenizer.collect(Ljava.lang.String;II)V(Pa
odingTokenizer.java:146)
at
net.paoding.analysis.knife.CJKKnife.dissect(Lnet.paoding.analysis.knife.Collecto
r;Lnet.paoding.analysis.knife.Beef;I)I(Optimized
Method)
at
net.paoding.analysis.knife.SmartKnifeBox.dissect(Lnet.paoding.analysis.knife.Col
lector;Lnet.paoding.analysis.knife.Beef;I)I(Optimized
Method)
at
net.paoding.analysis.analyzer.PaodingTokenizer.next()Lorg.apache.lucene.analysis
.Token;(PaodingTokenizer.java:182)
at
org.apache.lucene.index.DocumentWriter.invertDocument(Lorg.apache.lucene.documen
t.Document;)V(DocumentWriter.java:143)
at
org.apache.lucene.index.DocumentWriter.addDocument(Ljava.lang.String;Lorg.apache
.lucene.document.Document;)V(DocumentWriter.java:81)
at
org.apache.lucene.index.IndexWriter.addDocument(Lorg.apache.lucene.document.Docu
ment;Lorg.apache.lucene.analysis.Analyzer;)V(IndexWriter.java:307)
at
org.apache.lucene.index.IndexWriter.addDocument(Lorg.apache.lucene.document.Docu
ment;)V(IndexWriter.java:294)
at testlucene.LuceneIndex.writeToIndex()V(LuceneIndex.java:64)
at testlucene.LuceneIndex.main([Ljava.lang.String;)V(LuceneIndex.java:24)
Original issue reported on code.google.com by dustclo...@gmail.com on 27 Jun 2008 at 8:48
Original issue reported on code.google.com by
dustclo...@gmail.com
on 27 Jun 2008 at 8:48