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.
The java project created from NFT wizard should always set some build target as a default one so that it won't complain when user builds it. If there is only Compiled Classes b.t. then it should be the default b.t., but in case of additional build steps like packaging, etc. it might make sense to have some of these steps as a default b.t. (perhaps the last one).
Java Project UI Spec should describe the wanted behaviour of modules which add new BuildTarget that depends on the Compiled Classes. Java module sets the Compiled Classes as default bt., but the module should override the default bt. by its bt.
a different module shouldn't just overrided the default. when the user creates a new project the compiled classes b.t. should be the default b.t. when the user creates a new build target it should then become the default -regardless of what it is. a checkbox in the new b.t. wizard will let the user change this behavior... it will be in the spec should it not be clear here.
Java modules now sets Compiled Classes as default bt. The other modules or New bt. wizard can override it by whatever thay want.
the spec has been updated... check http://projects.netbeans.org/uispecs/java/JavaProjectsUISpec.html#v.iv scroll down to step 1. the check box there determines if the new build target should be used as default.
verified
As described in http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the current work on projects prototype has been stopped. Marking issue as CLOSED.