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.
When clicking thru javadoc I was often surprised when can be hidden under some classes: RemoteBuildSupport is in fact a factory for creation of Compilable objects BuildConfiguration is also a helper class with two static methods BuildTargetTranferable (as reported in other bug) could be factory method as well. ActionFactory is a factory (but that is at least easy to get from the name ;-) But all these cases lead me to this suggestion: Why not have just one class with such factory methods? This is common in java.util.Collections or in org.netbeans.spi.looks.Looks and in other places as well. This might make the javadoc more compact (less classes) and for those who know this convention also easier to read.
BuildUtils created to collect factory methods form BuildConfiguration, RemoteBuildSupport, and BuildTargetTranferable. ActionsFactory let separated because factory methods it contains are not directly "project related" (unlike the methods collected in BuildUtils).
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 VERIFIED --->
---> CLOSED