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.

Bug 219646 - NullPointerException at org.apache.maven.index.context.DefaultIndexingContext.acquireIndexSearcher
Summary: NullPointerException at org.apache.maven.index.context.DefaultIndexingContext...
Status: RESOLVED DUPLICATE of bug 219645
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-06 21:47 UTC by Maksim Khramov
Modified: 2012-10-08 05:20 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 193178

Attachments
stacktrace (4.98 KB, text/plain)
2012-10-06 21:47 UTC, Maksim Khramov 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Maksim Khramov 2012-10-06 21:47:45 UTC 
Build: NetBeans IDE Dev (Build 201210060002)
VM: Java HotSpot(TM) 64-Bit Server VM, 20.5-b03, Java(TM) SE Runtime Environment, 1.6.0_30-b12
OS: Windows 7

Stacktrace: 
java.lang.NullPointerException
   at org.apache.maven.index.context.DefaultIndexingContext.acquireIndexSearcher(DefaultIndexingContext.java:488)
   at org.apache.maven.index.context.DefaultIndexingContext.getGroups(DefaultIndexingContext.java:791)
   at org.apache.maven.index.context.DefaultIndexingContext.getAllGroups(DefaultIndexingContext.java:764)
   at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl$9.run(NexusRepositoryIndexerImpl.java:746)
   at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl$7.run(NexusRepositoryIndexerImpl.java:716)
   at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl$7.run(NexusRepositoryIndexerImpl.java:702)
Comment 1 Maksim Khramov 2012-10-06 21:47:47 UTC 
Created attachment 125518 [details]
stacktrace
Comment 2 Milos Kleint 2012-10-08 05:20:00 UTC 

*** This bug has been marked as a duplicate of bug 219645 ***