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 43380 - Would be nice if UI supported a complete class name when user create a new class
Summary: Would be nice if UI supported a complete class name when user create a new class
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: All All
: P4 blocker (vote)
Assignee: Petr Hrebejk
URL:
Keywords:
Depends on:
Blocks: 41535
  Show dependency tree
 
Reported: 2004-05-17 15:37 UTC by vbrabant
Modified: 2007-09-26 09:14 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vbrabant 2004-05-17 15:37:25 UTC
When I am creating a class, I like to give his
full class name like org.vbb.unittest.Translation.
Before NB4.0, it was not supported, but you
received a clear message or ignored the path and
keep the classname.
Now, it is also not supported, but give no message
at all and ignore your class name. Finally, I had
a Class.java file in the default package.
Comment 1 Jesse Glick 2004-05-17 16:33:15 UTC
Probably reasonable that the Java target chooser would autocreate
missing package directories if you specify a FQN. Not sure exactly how
it should work in the GUI, however - there is a Name field as well as
a Package editable combo. I believe you can enter an explicit package
in the Package field, but if you specify a package prefix in the Name
field it does not grok this? Behavior of wizard needs to be refined.
Comment 2 Jesse Glick 2004-05-17 16:33:52 UTC
Defect, I think, since it lets you enter a FQN that does not interact
properly with the supplied package. Should either handle the package
prefix, or forbid it.
Comment 3 Petr Hrebejk 2004-05-19 12:32:53 UTC
Making enhancement again. (ClassName no longer does permit to fill in
package prefix).

And closing as wontfix. Because there is the package field where the
user is supposed to wite (or select) the package name. (It also should
now be filled with reasonable context sensitive default).
It would be pretty messy to have the package name in both class and
package field and to try to implement some "smart" gess about what the
package should be.
Comment 4 Quality Engineering 2007-09-20 09:47:59 UTC
Reorganization of java component