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.
i normally start netbeans from the command line so i can see any standard/error output (i like to know what's going on). a while ago, code was added that displays a stack trace which seems to be for developer information only. the header is 'java.lang.Exception: Stack trace'; attached is text for one. the problem is, these stack traces get displayed many times and flood the screen. they make it impossible to pick out the real exceptions and worse, cause some output to be lost as the output leaves the scroll buffer. my scroll buffer is 2000 lines which should be plenty. the code which is generating the stack traces seems to be associated with getting information about dependent projects in web projects, possibly in or called by the 'toString' method. please remove these stack traces or provide a command line switch to supress only them.
Created attachment 20135 [details] stack trace
Alvin, which build have you used? Do you have any reproducible steps how to raise this exception? Thanks!
i'm using daily 20040131 on win2k. the default jdk is 1.5 but the projects i created use 1.4.2. it's been happenning with the daily builds for at least a couple of weeks or so. this is how i get it: 1. create a (non-web) j2se library project. (mine uses jdk 1.4.2) 2. create a web project with existing sources. (mine is jdk 1.4.2) 3. go to project properties-->Compiling Sources 4. click the add project button 5! navigate to the directory which contains the library project. stack traces show up when the library project is displayed in the file chooser. 6! add the library project to the web project. more stack traces. 7! now, whenever the IDE is started, the project is opened, or the project properties are displayed, the stack trace shows up. the weird part is that whenever a screen that contains the dependent project's name/icon has to be redrawn you get the stack traces again. since the icon is likey not the problem, i'm guessing the first place to look is the toString method for an object that represents the dependent library. this problem does not occur adding the same library project to a non-web (J2SE) project.
so far, the stack traces haven't shown up in the 20050202 build. somebody must have fixed it since the day before...
duplicate of fixed issue *** This issue has been marked as a duplicate of 53823 ***