Bug 11406 - ActionPerformed() method in AbstractAction not found
Summary: ActionPerformed() method in AbstractAction not found
Status: RESOLVED DUPLICATE of bug 10701
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows NT
: P3 major (vote)
Target Milestone: 2.0 M5   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-14 16:05 EST by Philip Borlin CLA
Modified: 2002-04-30 07:01 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Borlin CLA 2002-03-14 16:05:45 EST
All JDK/JREs are Windows JDK/JREs from Sun.  I am using the stable build of
Eclipse from February 14, 2002.

When I tried to change my JRE from 1.3.0 to 1.4.0 and import the corresponding
rt.jar for 1.4.0, I noticed that javax.swing.AbstractAction outline does not
contain the method actionPerformed(ActionEvent ae).  When I compile my code I
get the error: "The method actionPerformed(java.awt.event.ActionEvent) is
undefined for the type javax.swing.AbstractAction".  This is huge since a good
portion of my program will not compile because I (correctly) assume all over my
code that AbstractAction has the actionPerformed(ActionEvent ae) method.

I have tried creating new projects and the same behavior is exhibited.  This
problem does not occur when I use either 1.3.0 or 1.3.1.
Comment 1 Olivier Thomann CLA 2002-03-14 16:15:38 EST
This is due to a change in the rt.jar between 1.4 and 1.3.x. In 1.3.x abstract classes have a 
abstract methods for methods inherited by their interfaces. This is when the target is 1.1 vms. 
However, the JDK1.4 libraires are compiled to target 1.2 VMs and these abstract methods are 
removed.
This is a duplicate of 10701. You can fix the errors by setting the Compiler compliance 
level to 1.4 instead of 1.3. Go to:
Preferences>Java>Compiler>JDK Compliance>Compiler 
compliance level. Set this value to 1.4. Then it will recompile your code and it should fix all 
errors related to this problem.

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