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: | New Class Wizard should check if the class name is unique before continuing | ||
---|---|---|---|
Product: | platform | Reporter: | jhoffman <jhoffman> |
Component: | Window System | Assignee: | David Strupl <dstrupl> |
Status: | CLOSED FIXED | ||
Severity: | major | CC: | asunhachawee, mvenkatraman |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
jhoffman
2000-10-11 23:45:57 UTC
it does not apply only to Java class, but also for other templates Fixed in the main trunk. Fixed in the release31. There is a case in which the check isn't done correctly. See issue 11324 for details. *** Issue 11324 has been marked as a duplicate of this issue. *** Pasting the description from the duplicate here: Create the test object in the root of a filesystem. Now try to create the duplicate: 1. Bring up the wizard from File->New (not with right-click) 2. Choose the object type, hit next 3. Enter the name of the same-named object and indicate the root of the filesystem as the target location. 4. Next is grayed out at this point. 5. Hit the back button to see the template selection page. 6. Hit Next again. 7. Now Next is (incorrectly) enabled and you hit the bug. The validity check is not done after move from templates panel to targetPanel. Changing version and making it P3 - the steps are quite rare. Fixed in both [dev] and [release32]. Target milestone 3.2 verified Resolved for 3.4.x or earlier, no new info since then -> closing. |