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 5892 - When the manifest for a test module is not found at IDE startup, the Modules node does not behave robustly.
Summary: When the manifest for a test module is not found at IDE startup, the Modules ...
Status: CLOSED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: All All
: P4 normal (vote)
Assignee: akemr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-03-01 21:15 UTC by Jesse Glick
Modified: 2008-12-22 17:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 2000-03-01 21:15:45 UTC 
I.e. install a test module; delete or disable the manifest (as if, say, it was on a network drive which crashed); and then restart the IDE. It should just tell you that the manifest was not found, s
kip that module, and otherwise be OK. But it seems that this screws up the TestModuleItem (its .description is null, I think?) and the whole Modules node breaks. You need to shut down the IDE, restore
 the manifest or edit installedModules.xml, and restart to fix it.
Comment 1 Jesse Glick 2001-01-19 11:47:59 UTC 
Assuming splitloaders_jan2001 is merged, will be a moot point: no test modules
as such. Hopefully JAR entries are more robust.
Comment 2 akemr 2002-02-20 07:53:08 UTC 
Reopen to look at if it works.
Comment 3 akemr 2002-02-20 07:53:57 UTC 
I tried it on dev build and it works fine.
Comment 4 Jesse Glick 2002-02-20 13:15:56 UTC 
Indeed, there is no module installation from manifest any more, so
there can be no bug.
Comment 5 Quality Engineering 2003-07-01 16:26:06 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.