Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318201 - New methods tagged as @noreference added to an abstract class should not be reported as new API
Summary: New methods tagged as @noreference added to an abstract class should not be r...
Status: CLOSED INVALID
Alias: None
Product: PDE
Classification: Eclipse Project
Component: API Tools (show other bugs)
Version: 3.6   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-06-28 11:57 EDT by Olivier Thomann CLA
Modified: 2010-06-28 12:40 EDT (History)
3 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 Olivier Thomann CLA 2010-06-28 11:57:20 EDT 
In HEAD, org.eclipse.osgi has some errors because new methods tagged as @noreference are reported as part of the new API.
@noreference methods should never be part of the API.
Comment 1 Olivier Thomann CLA 2010-06-28 12:02:24 EDT 
This should probably be fixed in 3.6.1.
Darin, your call.
Comment 2 Olivier Thomann CLA 2010-06-28 12:20:07 EDT 
@since errors are a consequence of reporting these new methods as part of the API.
Comment 3 Olivier Thomann CLA 2010-06-28 12:40:20 EDT 
Closing as INVALID.
I can no longer reproduce the problem and the methods reported as a problem are not new methods.
No idea what happened.