This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Build: NetBeans IDE Dev (Build 201007090001) VM: Java HotSpot(TM) Client VM, 16.0-b13, Java(TM) SE Runtime Environment, 1.6.0_18-b07 OS: Windows 7 User Comments: GUEST: Performing latest plugin update. Stacktrace: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 38148 at org.apache.lucene.util.BitVector.get(BitVector.java:91) at org.apache.lucene.index.SegmentTermDocs.next(SegmentTermDocs.java:125) at org.apache.lucene.index.DocumentsWriter.applyDeletes(DocumentsWriter.java:956) at org.apache.lucene.index.DocumentsWriter.applyDeletes(DocumentsWriter.java:918) at org.apache.lucene.index.IndexWriter.applyDeletes(IndexWriter.java:4339) at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java:3579)
Created attachment 100745 [details] stacktrace
Created attachment 100748 [details] stacktrace
Do you know much about Lucene usage?
Could be caused by corrupted index files, or by a bug in lucene or its usage by nexus indexer IMO. Given the large number of reports, a random corruption of index files is most probably not the case. I found a similar issue at https://issues.apache.org/jira/browse/LUCENE-2666 which is for a newer lucene version, but the comments section mentioned that the way of using lucene can be wrong in that particular case. In trunk, both lucene and nexus indexer changed recently. Lucene was upgraded from 2.4.1 to 2.9.3, and nexus indexer from 2.0.0 to 3.0.2. Closing worksforme now and let's see if new reports appear with daily (or 7.0) builds.