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 45841 - "Move Class" have problems with -J-Dorg.netbeans.spi.jroject.support.ui.packageView.TRUNCATE_PACKAGE_NAMES=true
Summary: "Move Class" have problems with -J-Dorg.netbeans.spi.jroject.support.ui.packa...
Status: RESOLVED DUPLICATE of bug 45996
Alias: None
Product: editor
Classification: Unclassified
Component: Refactoring (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-02 14:45 UTC by Jan Lahoda
Modified: 2007-04-03 18:02 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Patch that seems to fix the problem. (1.08 KB, patch)
2004-07-02 14:47 UTC, Jan Lahoda 		Details | Diff
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 Jan Lahoda 2004-07-02 14:45:23 UTC 
NB trunk build 200407011917, JDK1.5.0-beta2-b51.

Try to run the IDE with
-J-Dorg.netbeans.spi.jroject.support.ui.packageView.TRUNCATE_PACKAGE_NAMES=true
(makes the package names shorter in the Projects
view). Now, try to invoke the "Move Class" dialog
with some deeply nested packages in the project.
Try to look at the content of the "To Package:"
combo. The packages listed here use the short for
(which is illegal), instead of the full form. It
seems that it uses "getDisplayName()", while
"getName()" would work OK.

I am attaching a patch that seems to fix the problem.
Comment 1 Jan Lahoda 2004-07-02 14:47:10 UTC 
Created attachment 16122 [details]
Patch that seems to fix the problem.
Comment 2 Jan Becicka 2004-07-12 09:59:49 UTC 

*** This issue has been marked as a duplicate of 41448 ***
Comment 3 Jan Lahoda 2004-07-12 10:40:54 UTC 
Hi,
    you have probably duplicated this bug against icorrect bug. The
issue #41448 is an umbrella issue "[umbrella] track remaining open
issues in modules". Or do I miss something?
Comment 4 Jan Lahoda 2004-07-12 12:26:32 UTC 
The correct issue number is #45996.
Comment 5 Jan Lahoda 2004-07-12 12:26:45 UTC 

*** This issue has been marked as a duplicate of 45996 ***