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 62521 - IOException: No suite.dir defined
Summary: IOException: No suite.dir defined
Status: RESOLVED INVALID
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-17 21:50 UTC by rrochat
Modified: 2008-06-19 22:36 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
stack trace (13.38 KB, text/plain)
2005-08-17 21:52 UTC, rrochat
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rrochat 2005-08-17 21:50:28 UTC
I temporarily removed a project from a suite and later tried to add it back.
I got the following when I tried to look at the project properties (right click
on the project node and select "Properties"): 

java.io.IOException: No suite.dir defined from
D:\netbeans-scratch\ChimeraSuite\libpatches
	at
org.netbeans.modules.apisupport.project.universe.ModuleList.getModuleList(ModuleList.java:110)
	at
org.netbeans.modules.apisupport.project.universe.ModuleList.getModuleList(ModuleList.java:84)
	at
org.netbeans.modules.apisupport.project.NbModuleProject.getModuleList(NbModuleProject.java:636)

Yes, clearly a user error (I had not recreated the suite.properties file),
and this may be irrelevant if there is a nice gui for making modules be
standalone and moving them between suites, but I thought I'd file it
while I saw it.

more complete stack trace attached
Comment 1 rrochat 2005-08-17 21:52:06 UTC
Created attachment 24010 [details]
stack trace
Comment 2 Martin Krauskopf 2005-08-18 12:03:25 UTC
> this may be irrelevant if there is a nice gui for making modules be standalone
and moving them between suites

As a normal modules (standalone, suite-components, nb-cvs) have their
customizers, suite project has also special customizer. So just go to a suite's
properties and move, remove, delete its components as you want. So probably, as
you suppose, INVALID. I would be happy if you test it as much as you can since
this piece of code wasn't tested by developers too much yet. Thanks ;)
Comment 3 Jesse Glick 2005-08-18 15:17:32 UTC
Leaving open as a robustness bug (should recover better than this), but yes the
suite properties dialog is the proper way to do it.
Comment 4 Jesse Glick 2008-06-19 22:36:28 UTC
Too old, and the code for handling broken NB platform references has been edited many times since then.