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.

Bug 129057 - prevent new projects from being added to pointless parent projects / folders
Summary: prevent new projects from being added to pointless parent projects / folders
Status: RESOLVED WONTFIX
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Infrastructure (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-03 21:45 UTC by kawazu428
Modified: 2009-10-23 10:16 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description kawazu428 2008-03-03 21:45:42 UTC 
Situation: Been using NetBeans to create a module suite, added a bunch of modules to that. By then, using "New Project"
/ "NetBeans Module" always pre-sets "Project Location" to be the folder of the module suite this module belongs to. Fine.

However, this happens regardless of whether or not there's any meaning in putting a newly created project to that very
top-level folder. Especially, say, creating a new maven2 artifact, some sort of Java EE application, ..., obviously not
at all belonging to a module suite, the "New Project" wizard should offer a more sane "Project Location". 

(Note: This is IMHO more or less related to #116262 , and it is same as annoying...)
Comment 1 Milos Kleint 2008-03-04 09:26:04 UTC 
that's how the project location works. The last project location is remembered and offered next time with the assumption
you will create new projects at the same location. 

works as designed.
Comment 2 kawazu428 2008-03-04 09:40:19 UTC 
I don't argue against "works-as-designed" here, but at the very least in the situation given ("module suite" use case,
"enterprise application" use case) the "works-as-designed" approach seems pointless as soon as the newly created project
is something that _surely_ never will be in some relation to the project created before. 

- Having just created a module in a module suite, assuming the next module to also be part of that suite seems logical.
- Having just created an enterprise application, assuming an EJB module to be created will be part of this application
also seems logical.
- Having just created a module suite and some modules however, throwing a newly created "web application" to the module
suite folder doesn't at all seem logical. 

maybe indeed it works as designed, but, using it, it surely doesn't work as expected...
Comment 3 kawazu428 2008-03-20 22:10:09 UTC 
Re-opening this as an enhancement request. Indeed it has been pointed out that this behaviour is "the way project
location" works, and yet it's an annoying behaviour somewhat interfering with an "expected behaviour" of the IDE in the
situations outlined in the initial report. If this is "behaviour-by-design", is there any success likely in kindly
requesting a review of that very design?
Comment 4 Lukas Hasik 2008-04-10 21:41:11 UTC 
moving opened issues from TM <= 6.1 to TM=Dev
Comment 5 Milan Kubec 2009-10-23 10:07:18 UTC 
IMO any special heuristics that would decide what project type is allowed under what folder based on what user is
supposedly working on would be way more confusing (it would be really magic) than simple and easy to understand "use
last folder" rule. Sorry, closing the issue.

Re: "maybe indeed it works as designed, but, using it, it surely doesn't work as expected..." - if you ask 10 people
"what is expected" in this case I bet you will get 10 different opinions.
Comment 6 kawazu428 2009-10-23 10:15:43 UTC 
I get your point. Actually, this won't be much of an issue anyhow if #116262 is fixed. In this case, in my opinion, the
thing people would "expect" to happen is way clearer.