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.
NB200402171900, JDK1.4.2_03. Steps to reproduce: 1. Start the IDE with a clean userdir. 2. Open a Java file in the editor (for example examples/colorpicker/ColorPreview.java). 3. Go to Project Manager ("Project/Project Manager") and create a new project ("New..."). 4. During the switch to the new project, the attached FileNotFoundException (informational) is printed into the console. 5. Such an exception seems to be printed during each project-switch for all opened documents and for the TODO Window that are in the original (old) project. Although this exception is informational and not printed in a dialog, I think that it indicate that something is wrong.
Created attachment 13514 [details] The thrown FileNotFoundException
I usually don't want to argue about priority, beacuse it's useless, but this time....please try to reevaluate given priority and keep in mind that wrong priority may mean worse product in the end (because you are in fact dictating me what I will work on).
Passing to Milos. Honzo again, do you really think it's P2? It seems to me it has no end user impact al all....
*** Issue 40129 has been marked as a duplicate of this issue. ***
it seems the exception logging was added in revision 1.1.2.21 on 2003/05/30 12:39:52 by mslama. As far as I can tell, it's an old debugging message and has no influence on the functionality. The problem appeared because of my #39713 fix, which puts the windowssystem definition on the session layer, rather than the previous project layer. For now I assume it's not a real problem. Adding pzavadsky and mslama on CC for comments.
I'm taking the liberty of dropping the priority on this issue. Jan, this is definitely not a P2, no functionality is broken (and a windows user using runidew.exe won't even see the stack trace). I agree, something is strange, but we have really broken things to fix. Milos, if it's just commenting out a line of old debug logging and you know where it is, just comment it out. Otherwise please don't waste time on this.
Well, the log gets displayed in other situations as well (see http://openide.netbeans.org/servlets/ReadMsg?msgId=699619&listName=dev for ean example) so I would rather not comment it out.
The priority was set to P2 mainly to find out whether the exception is harmless or not. I am also a bit afraid of the log full of meaningless exceptions, but I am fine with P4 if you are sure this will not break anything.
fixed by removing the exception stacktrace logging, the message log is preserved. please note that with the new build system, window system project switching is gone and should not trigger this error message in the log..
Well, I have not seen similar problems with new projects (stavbicka) builds.