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 44915 - Stop calling ClassPath.getClassPath with a null FileObject parameter
Summary: Stop calling ClassPath.getClassPath with a null FileObject parameter
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-16 04:22 UTC by Jesse Glick
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Typical stack trace; reason why it got to this point (some other bug I am too tired to file) is unimportant here (2.35 KB, text/plain)
2004-06-16 04:23 UTC, Jesse Glick 		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 Jesse Glick 2004-06-16 04:22:23 UTC 
040615 but this has been broken for a while.
Sometimes javamodel code calls CP.gCP with a null
FileObject, contrary to the Javadoc, causing a
stack trace to be printed. Should never do this.
Comment 1 Jesse Glick 2004-06-16 04:23:03 UTC 
Created attachment 15722 [details]
Typical stack trace; reason why it got to this point (some other bug I am too tired to file) is unimportant here
Comment 2 Martin Matula 2004-06-17 23:26:29 UTC 
Fixed.

Checking in src/org/netbeans/modules/javacore/RepositoryUpdater.java;
/cvs/java/javacore/src/org/netbeans/modules/javacore/RepositoryUpdater.java,v
 <--  RepositoryUpdater.java
new revision: 1.6; previous revision: 1.5
done