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 18257 - [Synchronization] duplicate methods after using new class wizard
Summary: [Synchronization] duplicate methods after using new class wizard
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
: 29841 (view as bug list)
Depends on: 10367 16799
Blocks: 29841
  Show dependency tree
 
Reported: 2001-12-02 04:30 UTC by _ jrichard
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments
the new class (390 bytes, text/plain)
2001-12-02 04:31 UTC, _ jrichard
Details
the base class (1.61 KB, text/plain)
2001-12-02 04:33 UTC, _ jrichard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description _ jrichard 2001-12-02 04:30:17 UTC
I used the new class wizard to create a class that extended
a base class.  I specified the methods to override in the 
wizard.  

But, when I clicked "Finish" a box popped up asking me if I wanted
to reconcile my new class with my base class.  I clicked "Process All"
and it (I assume it did) inserted a duplicate method.  I'll attach
the base and new classes.
Comment 1 _ jrichard 2001-12-02 04:31:50 UTC
Created attachment 3650 [details]
the new class
Comment 2 _ jrichard 2001-12-02 04:33:50 UTC
Created attachment 3651 [details]
the base class
Comment 3 _ jrichard 2001-12-02 04:43:14 UTC
BTW: the name of the box that came up was the "Confirm Changes"
dialog box.

Just a thought, but maybe it had something to do with the
fact that ByteBuffer wasn't in the import statement list.
(I can't think of another reason why I'd be asked to add
the same method twice, unless it is a timing issue.)

Also, I've found that this is repeatable.  It has happened
every time I've tried this with the new wizard.
Comment 4 _ ttran 2001-12-02 10:19:41 UTC
-> java module
Comment 5 Svata Dedic 2001-12-10 16:57:36 UTC
This behaviour is "as designed" (that's why I am turning the issue
into a feature request -- it's a known deficiency of the design)
although it may seem strange. And yes, it is connected to the missing
import. The IDE should insert the method with fully qualified
parameter's type, but the infrastructure is not mature enough to allow
such things.
As the existing method's parameter type is not resolved, it is treated
as distinct from the base class' resolved one - that's why a new
method is inserted.

Tentatively setting milestone to 3.4, but the solution depends on name
resolver implementation.
Comment 6 Svata Dedic 2002-05-21 17:48:15 UTC
Cleaning up before 4.0 planning
Comment 7 Marek Grummich 2002-07-19 17:01:58 UTC
Target milestone was changed from not determined to TBD
Comment 8 dnoyeB 2003-01-07 17:18:10 UTC
*** Issue 29841 has been marked as a duplicate of this issue. ***
Comment 9 Martin Matula 2004-11-11 17:20:35 UTC
This issue is no longer relevant.