[
https://issues.apache.org/jira/browse/MINDEXER-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965271#comment-17965271
]
Olivier Lamy commented on MINDEXER-26:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-indexer#483|https://github.com/apache/maven-indexer/issues/483].
> NPE from IndexWriter.isLocked in DefaultIndexingContext.prepareCleanIndex
> -------------------------------------------------------------------------
>
> Key: MINDEXER-26
> URL: https://issues.apache.org/jira/browse/MINDEXER-26
> Project: Maven Indexer (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 4.0.0
> Environment: VM: Java HotSpot(TM) 64-Bit Server VM, 19.0-b09,
> Java(TM) SE Runtime
> Environment, 1.6.0_23-b05
> OS: Windows 7
> Reporter: Jesse N. Glick
> Priority: Major
> Fix For: 4.1.1
>
>
> http://netbeans.org/bugzilla/show_bug.cgi?id=197346 reported by a NetBeans
> user in a build embedding Maven Indexer 4.0.0.
> {noformat}
> if ( IndexWriter.isLocked( indexDirectory ) )
> {
> IndexWriter.unlock( indexDirectory );
> }
> {noformat}
> Looks like {[indexDirectory}} is null, perhaps due to {{close}} having been
> called, and this code does not check for that (other code in the same class
> does). Can probably be guarded with a simple null check?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
