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 49915 - Exceptions after deleting nbproject folder
Summary: Exceptions after deleting nbproject folder
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Infrastructure (show other bugs)
Version: 4.x
Hardware: All All
: P4 blocker (vote)
Assignee: Milos Kleint
: 51873 (view as bug list)
Depends on:
Blocks: 41535
  Show dependency tree
Reported: 2004-10-05 04:44 UTC by Pavel Buzek
Modified: 2008-02-21 08:52 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Buzek 2004-10-05 04:44:49 UTC
create a project, play with it, then go to files
view and delete the nbproject folder... 
See the result. 

You will get a number of NPEs etc.
Tested with web project and j2se project.

Maybe it should not be allowed to delete nbproject
or the project should first be closed. In any way
it requires special handling.
Comment 1 David Konecny 2004-10-05 10:46:01 UTC
Yes, this is problem, but not P2. Honestly, my first thought was that
it is WONTFIX. Is not this user's problem? They should know what they
are doing. There is online help explaining importance of these files.
Comment 2 Jesse Glick 2004-10-05 15:39:44 UTC
Agreed. "When I open the About box of SuperPro SpreadSheet GL+ and
press Ctrl-Alt-Shift-F12 three times, my system crashes!" "Well don't
do that then."
Comment 3 _ ludo 2004-10-05 15:55:56 UTC
crashes are not acceptable in Java... That's why it's a virtual machine.
So next real scenario: after a cvs update, the content of the
nbproject in entirely in conflict mode...
Same NPE?
I did not try, but this is a rela enterprise scenarion. If I don;t
have a good answer, I'll move back to P2.
Comment 4 Jesse Glick 2004-10-05 16:23:14 UTC
If the system is unable to recover after there are merge conflicts in
nbproject/, that is of course more serious.

Note however that there are various enhancements that are not planned
for 4.0 in the area of validating nbproject contents before opening,
which would probably apply also to changes made while the project is
open (or otherwise loaded). Already filed separately.
Comment 5 Jesse Glick 2004-11-29 21:29:28 UTC
Cf. also #42422.
Comment 6 Jesse Glick 2004-11-29 21:29:39 UTC
*** Issue 51873 has been marked as a duplicate of this issue. ***
Comment 7 chaase3 2006-09-06 19:35:57 UTC
At the recent NB 5.5 Q build
(netbeans-5_5-qbuild-bin-200608181330-windows-18_Aug_2006_1330.exe), if you
click Open Project for an enterprise app that doesn't have an nbproject
directory, NB hangs completely with the message "EAR?????" in the dialog. I have
to kill NB with a 3-fingered salute in order to get out. This seems unacceptable
from a user's point of view. (How this happened is that I got mixed up between
being able to delete build-impl.xml and have NB regenerate it, and being able to
delete the whole nbproject directory. You really have to expect users to be this
stupid, you know, if you have any pretensions to building a robust user interface.)
Comment 8 Milos Kleint 2008-02-21 08:52:29 UTC
tried with latest 6.1 build (Feb 14).
created a j2se application, in Files view deleted the nbproject directory. No exceptions.

closing as fixed.