Bug 31475 - class must implement the inherited abstract method, but cannot override it
Summary: class must implement the inherited abstract method, but cannot override it
Status: RESOLVED DUPLICATE of bug 31398
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P3 critical (vote)
Target Milestone: 2.1 RC1   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-10 12:09 EST by Nikolay Entin CLA
Modified: 2003-02-10 17:48 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nikolay Entin CLA 2003-02-10 12:09:50 EST
Can't compile quite old class.
This is new problem of M5 (is not reproducible with M4):
I've got a class, which extends 
org.eclipse.gef.ui.parts.DomainEventDispatcher
which for itself extends 
org.eclipse.draw2d.SWTEventDispatcher
this one extends abstract
org.eclipse.draw2d.EventDispatcher

in my class I have the following error reports (for other similar methods too):
"This class must implement the inherited abstract method 
EventDispatcher.getCursorTarget(), but cannot override it since it is not 
visible from DiagramEventDispatcher. Either make the type abstract or make the 
inherited method visible."

getCursorTarget is implemented in SWTEventDispatcher and subclasses (including 
my one) do not override it. So the implementation is provided, but somehow JDT 
doesn't determine it.

Don't know if that relevant, but my class is defined inside another one:
private static class DiagramEventDispatcher extends DomainEventDispatcher {...}
P.S. used org.eclipse.gef/draw2d, which are from 20/08/02
Comment 1 Olivier Thomann CLA 2003-02-10 13:57:57 EST
Could you please send the source code for the class DiagramEventDispatcher?
Comment 2 Olivier Thomann CLA 2003-02-10 14:06:05 EST
Could this be a duplicate of bug 31398?
Comment 3 Philipe Mulet CLA 2003-02-10 17:48:33 EST
Very likely, we almost have a patch ready (will attempt to release it for 
integration tomorrow).

*** This bug has been marked as a duplicate of 31398 ***