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 251520 - NullPointerException: The FileSystem parameter cannot be null
Summary: NullPointerException: The FileSystem parameter cannot be null
Status: RESOLVED DUPLICATE of bug 251527
Alias: None
Product: cnd
Classification: Unclassified
Component: Code Model (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: issues@cnd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-31 00:58 UTC by jdavidbakr
Modified: 2015-09-23 21:29 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 216469

Attachments
stacktrace (4.30 KB, text/plain)
2015-03-31 00:58 UTC, jdavidbakr 		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 jdavidbakr 2015-03-31 00:58:15 UTC 
Build: NetBeans IDE Dev (Build 201503270001)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.25-b01, Java(TM) SE Runtime Environment, 1.7.0_25-b15
OS: Mac OS X

User Comments:
jdavidbakr: Asked for tool collections to be fixed when booting, I said Yes and got the error.




Stacktrace: 
java.lang.NullPointerException: The FileSystem parameter cannot be null
   at org.openide.util.Parameters.notNull(Parameters.java:89)
   at org.netbeans.modules.cnd.modelimpl.csm.core.ProjectBase.getUniqueName(ProjectBase.java:457)
   at org.netbeans.modules.cnd.modelimpl.csm.core.ProjectBase.<init>(ProjectBase.java:183)
   at org.netbeans.modules.cnd.modelimpl.csm.core.LibProjectImpl.<init>(LibProjectImpl.java:88)
   at org.netbeans.modules.cnd.modelimpl.csm.core.LibProjectImpl.createInstance(LibProjectImpl.java:113)
   at org.netbeans.modules.cnd.modelimpl.csm.core.LibraryManager$LibraryEntry.createUID(LibraryManager.java:621)
Comment 1 jdavidbakr 2015-03-31 00:58:17 UTC 
Created attachment 152939 [details]
stacktrace
Comment 2 Vladimir Kvashin 2015-09-23 21:29:56 UTC 

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