The slowness report
seems to indicate that the code completion is blocked by initialization of
As the content of the indexing context is likely to be needed whenever one edits a pom.xml I suggest to preload it as soon as the pom.xml is opened in editor or when a maven project is openened.
At minimum (to lower the priority) the maven CC support needs to warn the user that it is about to perform a lengthy operation via http://bits.netbeans.org/dev/javadoc/org-netbeans-modules-editor-completion/org/netbeans/spi/editor/completion/CompletionResultSet.html#setWaitText(java.lang.String
Any reports in 7.0? Tonda did some related fix recently I think.
Should you look at report 445497 closely, you'd find out that it is from 7.0Beta.
> At minimum (to lower the priority) the maven CC support
> needs to warn the user that it is about to perform a lengthy operation.
Decreasing to P3. The warning to the user about XML CC in general is implemented in issue 192625.
this should have been fixed lately as indexing is triggered by indexer queries, but the queries no longer block on completion of the indexing, instead we notify the user that indexing takes place only. (and return partial results from indexes already ready for consumption)
*** This bug has been marked as a duplicate of bug 200263 ***