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 257655 - NullPointerException at org.netbeans.gradle.project.util.NbFileUtils.getFileFromASubDir
Summary: NullPointerException at org.netbeans.gradle.project.util.NbFileUtils.getFileF...
Status: NEW
Alias: None
Product: third-party
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: attila.kelemen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-21 04:04 UTC by ajeets1978
Modified: 2016-01-22 08:36 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 222223

Attachments
stacktrace (1.03 KB, text/plain)
2016-01-21 04:04 UTC, ajeets1978 		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 ajeets1978 2016-01-21 04:04:02 UTC 
Build: NetBeans IDE 8.1 (Build 201510222201)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.66-b17, Java(TM) SE Runtime Environment, 1.8.0_66-b17
OS: Mac OS X

User Comments:
ajeets1978: Reopened the existing gradle project




Stacktrace: 
java.lang.NullPointerException
   at org.netbeans.gradle.project.util.NbFileUtils.getFileFromASubDir(NbFileUtils.java:154)
   at org.netbeans.gradle.project.query.GradleCacheByBinaryLookup$NewFormatCacheResult.getRoots(GradleCacheByBinaryLookup.java:135)
   at org.netbeans.gradle.project.query.GradleCacheJavadocForBinaryQuery$2.getRoots(GradleCacheJavadocForBinaryQuery.java:56)
   at org.netbeans.modules.javadoc.search.JavadocRegistry.readRoots(JavadocRegistry.java:180)
   at org.netbeans.modules.javadoc.search.JavadocRegistry.getDocRoots(JavadocRegistry.java:131)
   at org.netbeans.modules.javadoc.search.IndexBuilder.refreshIndex(IndexBuilder.java:183)
Comment 1 ajeets1978 2016-01-21 04:04:04 UTC 
Created attachment 158200 [details]
stacktrace
Comment 2 attila.kelemen 2016-01-22 08:36:37 UTC 
Do you experience any problem after this exception? Anyway, I can see the problem: A directory in Gradle's cache became unreadable just right after the plugin checked for its existence. Regardless, I'll fix this but I would like to know if you have noticed any adverse effect after this exception.