Bug 122043 - Incremental Compilation Bug: not checking exceptions on super in some case
Summary: Incremental Compilation Bug: not checking exceptions on super in some case
Status: REOPENED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.5.0   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-23 19:15 EST by Ron Bodkin CLA
Modified: 2009-08-30 02:50 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 Ron Bodkin CLA 2005-12-23 19:15:20 EST
I ran into a bug in incremental compilation that I'm now having a hard time replicating. I had a Servlet class like this:

public class MockServletHangForever extends MockServletCpuHog {
    protected void doPost(HttpServletRequest request, HttpServletResponse response) {
        super.doPost(request, response); 
...
}

The AspectJ compiler incrementally accepted this even though the signature of super.doPost is 
protected void HttpServlet.doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException

On a full compilation the ajc compiler catches this, of course. And once I have made changes like this, I can't seem to get the incremental compiler to accept it again.

However, I discovered this bug because an ant build complained about it and I saw there were no errors in the Eclipse view which had been compiled incrementally!
Comment 1 Wes Isberg CLA 2006-02-17 15:02:32 EST
This kind of thing happens to me in eclipse when I'm only displaying problems for the selected resource and another error in the compile (on another file/resource) halts the process before this error would have been detected.  Do you think that might be what happened?  If you've seen this since or can replicate it reliably (with all problems shown), please provide more details.  Otherwise, would you mind closing or permitting us to close this bug?
Comment 2 Ron Bodkin CLA 2006-02-17 15:44:00 EST
I haven't seen the bug since. I'm pretty sure I wasn't using a filter to restrict the set of problems shown, although I will admit that after two months I'm not 100% sure.
Comment 3 Eclipse Webmaster CLA 2009-08-30 02:50:34 EDT
LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated.