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 201101270001) VM: Java HotSpot(TM) 64-Bit Server VM, 17.1-b03-307, Java(TM) SE Runtime Environment, 1.6.0_22-b04-307-10M3261 OS: Mac OS X User Comments: musilt2: updating index. In this build should be already new lucerne and maven indexer. Stacktrace: java.lang.NullPointerException at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl$NotifyingIndexCreator.updateDocument(NexusRepositoryIndexerImpl.java:550) at org.apache.maven.index.context.IndexUtils.updateDocument(IndexUtils.java:157) at org.apache.maven.index.context.IndexUtils.updateDocument(IndexUtils.java:129) at org.apache.maven.index.updater.DefaultIndexUpdater.copyUpdatedDocuments(DefaultIndexUpdater.java:343) at org.apache.maven.index.updater.DefaultIndexUpdater.unpackIndexArchive(DefaultIndexUpdater.java:272) at org.apache.maven.index.updater.DefaultIndexUpdater.loadIndexDirectory(DefaultIndexUpdater.java:202)
Created attachment 105398 [details] stacktrace
beingIndexed is probably null, not related to Lucene 3.0 I will debug it.
I am not able to reproduce it :-( But if I understand it correctly it's a race condition. The indexLoadedRepo is guarded by write lock which is allocated per repository. But the NotifyIndexCreator.beingIndexed is static shared among all instances. When one loading completes it can overwrite the value by null. Making it instance variables (if more progress should be displayed at once) should solve it.
core-main #d981cdce09a3
Integrated into 'main-golden', will be available in build *201102160501* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/d981cdce09a3 User: Jesse Glick <jglick@netbeans.org> Log: #194767: NullPointerException at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl$NotifyingIndexCreator.updateDocument
*** Bug 194404 has been marked as a duplicate of this bug. ***
*** Bug 194713 has been marked as a duplicate of this bug. ***