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.
Observed in builds: dev-200205010100, QBE200204250100-200204260820
Created attachment 5616 [details] ide.log
I need some extra information : - do you have directory netbeans_home/tomcat401 before starting IDE ? - do you have netbeans_home/tomcat401/work subdirectory there ? It seems that somethink was missing.
If you mean either install_dir or user_dir by netbeans_home then not. It was clean instalation (unziped) with clean userdir.
I checked NetBeansIDE-dev-200205010100.zip and NetBeansIDE-dev-200205010100.tar.gz. Both contain tomcat401 directories with bundled Tomcat. So it looks that your instalation is corrupted. It has to work even without this dir but it is not critical issue now.
I am marking this bug as INVALID, because most likely you had a corrupted build. (There wasn't tomcat401 subdirectory there in install_dir).
We discussed the issue again with the reporter. The bug was caused by a strange unpacking of the build from the zip file. However there is a unreasonable copy operation at the first start : - empty "ide_install/tomcat401/work" directory is being copied to "user_dir/tomcat401_base/work" directory. I suggest simply to create new "user_dir/tomcat401_base/work" directory. I am changing the issue type to TASK.
we had wide discussion about this problem because we have in the IDE about 15 empty directories and we do not want to chack evry time, if these empty folders exist, it is not a bug for us empty dirs are in the IDE installation archives. it means, they are important for IDE. if your unzip SW thinks, it is not important for its, so it is its responsibility
Sorry but I still do not see NPE stack trace as a correct notification to user. You should at least notify what is missing.
I have to agree. Assuming, say, 25% of Windows Netbeans users will download archives rather than installers, and 25% of those use WinZip, then that's thousands of developers who see their (quality-certified) Netbeans builds throwing NPEs at startup every time, with no indication of what's wrong. Each one of them has to go through the IssueZilla and hopefully find this bug without wasting too much of their time. When an app throws NPEs at you, your confidence in that app drops. NPEs displayed to the user are simply unacceptable handling of a known, predictable, common error -- no matter whose fault that error is.
Maybe it would be usefull to document this on download page. The final solution depends on general policy so we should discuss it on nbdev.
Set target milestone to TBD
*** This issue has been marked as a duplicate of 26570 ***