Bug 155397 - [probably 3.2 compiler] Statically imported method not recognized
Summary: [probably 3.2 compiler] Statically imported method not recognized
Status: RESOLVED INVALID
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: DEVELOPMENT   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 1.6.1   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-28 10:51 EDT by Robert Munteanu CLA
Modified: 2008-06-10 15:54 EDT (History)
1 user (show)

See Also:

Attachments
The error reported when the static method is not detected. (50.06 KB, image/png)
2006-08-28 10:51 EDT, Robert Munteanu CLA 		no flags Details
Sample project with defect (3.82 KB, application/zip)
2006-09-05 06:30 EDT, Robert Munteanu CLA 		no flags Details
View All 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 Robert Munteanu CLA 2006-08-28 10:51:09 EDT 
Hi,

I have converted an existing java project to have aspectj capability. In a class which has defined a verify() method I cannot call a statically imported verify(Object) method, which is shown as a compiler error (The method verify() in the type XXXTest is not applicable for the arguments (YYY)).

Fully qualifying the static method ( i.e. EasyMock.verify(...) ) did fix the error.
Comment 1 Robert Munteanu CLA 2006-08-28 10:51:50 EDT 
Created attachment 48879 [details]
The error reported when the static method is not detected.
Comment 2 Matt Chapman CLA 2006-09-04 09:06:04 EDT 
Please could you attach a testcase. Thanks.
Comment 3 Robert Munteanu CLA 2006-09-05 06:30:23 EDT 
Created attachment 49390 [details]
Sample project with defect

Please check defects.StaticImportFailure
Comment 4 Matt Chapman CLA 2006-09-12 12:26:11 EDT 
Thanks for the testcase. I can reproduce this on Linux and Windows.
As the 3.2 Eclipse Java compiler handles this ok, I suspect this is another case that will be fixed by upgrading the AspectJ compiler.
Comment 5 Andrew Clement CLA 2008-01-22 12:22:37 EST 
hmm, i seem to get an error on that call to perform in a standard java project on eclipse 3.3.
Comment 6 Robert Munteanu CLA 2008-01-23 04:26:50 EST 
I think it's the same issue as in bug #159543 , which is also reported by me, so not an AJDT defect.
Comment 7 Andrew Clement CLA 2008-06-10 15:54:28 EDT 
Closing as per bug 159543 was closed.