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.
Summary: | Build failed when missing classes and invoking javadoc | ||
---|---|---|---|
Product: | java | Reporter: | Milan Kubec <mkubec> |
Component: | Project | Assignee: | Jan Jancura <jjancura> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 4.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Milan Kubec
2004-08-25 10:54:00 UTC
Too pathological to waste CPU time checking for it in advance, IMHO. Well, then it should be fixed another way, but bare link to build.xml cannot be exposed to user after build failed. User will see the link and click it and then what ..? Will fix the problem in the script? No, the user will create some source files! Why would you try to generate Javadoc if you had no source files?? Sorry, I really don't consider this important enough to fix. You can always construct some pathological situation that the IDE doesn't produce a perfect response for, but we're not going to fix all of them; there are more important things to spend time on. Sorry, I don't share your optimism, the world is far from ideal and user can easily invoke that action by accident if more project nodes are expanded in Projects view and he wants to invoke Javadoc for one of them, but does it for the other one. You get to this pathological situation by two clicks (e.g. on just created library). I'm reopening and lowering the priority, because I still think that the situation should be handled better than showing link to build script. As you like, but I have no plans to waste time on it. Resolving all issues with milestone "future" as LATER. If you feel strongly that it should be implemented please reopen and set the target milestone to "next". NetBeans.org Migration: changing resolution from LATER to WONTFIX |