This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 332840 - Wrong error about API change (Regression; works with 3.7M3)
Summary: Wrong error about API change (Regression; works with 3.7M3)
Status: CLOSED DUPLICATE of bug 331672
Alias: None
Product: PDE
Classification: Eclipse Project
Component: API Tools (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Olivier Thomann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-17 07:55 EST by Markus Schorn CLA
Modified: 2011-01-27 04:18 EST (History)
2 users (show)

See Also:

Attachments
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 Markus Schorn CLA 2010-12-17 07:55:37 EST 
Eclipse SDK, Version: 3.7.0, Build id: I20101208-1300

The following error is reported:

The interface org.eclipse.cdt.core.dom.ast.ISemanticProblem adds method getID() to org.eclipse.cdt.core.dom.ast.IProblemBinding that is not tagged as @noimplement	IProblemBinding.java	/org.eclipse.cdt.core/parser/org/eclipse/cdt/core/dom/ast	line 20	Compatibility Problem

However, the interface is tagged as @noimplement. Also the method is not actually added, it was moved from IProblemBinding into the new base interface ISemanticProblem.

I was not able to reproduce the problem with similar changes to other interfaces, it can be reproduced by using the HEAD version of plugin 'org.eclipse.cdt.core' with the helios cpp-package as a baseline.
Comment 1 Olivier Thomann CLA 2010-12-17 08:27:44 EST 
I'll take a look.
Comment 2 Dani Megert CLA 2011-01-26 10:43:05 EST 
Ping.
Comment 3 Olivier Thomann CLA 2011-01-26 10:45:23 EST 
under investigation.
Comment 4 Olivier Thomann CLA 2011-01-26 11:00:42 EST 
I cannot reproduce using HEAD. I am getting an unused api problem filter for the problem described in comment 0, but it actually works fine now.
I would recommend that you try the latest M5 build candidate and report back if you can reproduce.
Otherwise I would close as WORKSFORME.
Comment 5 Dani Megert CLA 2011-01-26 11:06:05 EST 
Maybe similar to the issue that I just filed today (bug 335430)?
Comment 6 Olivier Thomann CLA 2011-01-26 11:37:11 EST 
For me it looks like a duplicate of bug 331672.
Comment 7 Markus Schorn CLA 2011-01-27 04:14:54 EST 
Using Eclipse SDK Version: 3.7.0, Build id: I20110126-0800
I no longer see this issue.
Comment 8 Dani Megert CLA 2011-01-27 04:18:29 EST 

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