Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 260966

Summary:	Enable API tooling for the metadata bundle
Product:	[Eclipse Project] Equinox	Reporter:	Ian Bull <irbull>
Component:	p2	Assignee:	P2 Inbox <equinox.p2-inbox>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Ian Bull

2009-01-13 22:45:07 EST

API Tooling should be enabled in the metadata bundle.

Comment 1 John Arthorne

2009-01-14 14:08:50 EST

Since we're not declaring API in this release, what value would it give us?

Comment 2 Ian Bull

2009-01-14 14:21:01 EST

It was for the @noimplement / @noextend that we talked about. Maybe API tooling is not needed for this functionality to work.  If not, I can close this as invalid.

Comment 3 John Arthorne

2009-01-14 15:01:26 EST

I don't care either way, just wondering what the motivation was. I think unless it's an API package the API tooling will just ignore it anyway, but it might give you things like code-assist on the javadoc tags.

Comment 4 Ian Bull

2009-01-15 01:13:36 EST

Since I have already added the javadoc tags, the code assist is no longer needed.  We can close this now, and worry about this when we are going to specify API.