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 I create or open a certain project which expects nested projects, like NetBeans Platform Application project, any new project that I start creating has this "container" project's folder as its Project Location default. IMO having one NetBeans Platform Application project open does not mean that I will be creating only NetBeans Module projects (which usually belong under the App project). Having the default set in the current way can lead to frequent user errors when user does not pay enough attention to the Project Location field of new projects. Jesse, if you tell me how the current mechanism works, how I think it could be improved.
What is even more weird about the current mechanism is that after finishing with a Platform App project and its modules, closing *all* projects, next project I try to create (e.g. a pure general Java Application) still defaults its Project Location under the already closed Platform App project's folder.
As far as I know there is just one persisted location, used for any project type, via ProjectsChooser.projectFolder: the last parent dir used to create a new project. If the last project you created was a module inside a suite, then that is the default location for subsequent projects too. If you don't like that location, pick a different one. Simply opening a suite does not affect the default location for a new j2seproject. The exception is that in the wizard for a new module, if you elect to add to a suite (the default behavior if a suite is open), the default location for that wizard panel is set to the suite's dir; this is reset to the current projectFolder if you choose "standalone module".
(In reply to comment #2) > The exception is that in the wizard for a new module, if you elect to add to a > suite (the default behavior if a suite is open), the default location for that > wizard panel is set to the suite's dir One improvement I can make is that if you accept this default and Finish, the default project directory will be left untouched: core-main #f149670bf0c4
> One improvement I can make is that if you accept this default and Finish, > the default project directory will be left untouched. Good! This fixed the concern about completely unrelated projects being also put under the suite's dir if module was added previously. Could NetBeans Platform Application project be treated separately as well. I know it is only a template of Module Suite project (and placing the new suite under the opened suite may make sense), but maybe we can differentiate Platform Application template and not default it under the already existing suite/app project?
(In reply to comment #4) > Could NetBeans Platform Application project be treated separately as well. Suite project templates use the standard ProjectsChooser.projectFolder setting; there is no special handling for them. The special behavior is only for library wrapper module projects and suite component module projects.