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

Bug 328410

Summary:

Make API tools easier to consume

Product:

[Eclipse Project] PDE

Reporter:

Jeff McAffer <jeffmcaffer>

Component:

API Tools

Assignee:

PDE API Tools Inbox <pde-apitools-inbox>

Status:

NEW ---

QA Contact:

Severity:

normal

Priority:

CC:

Vikas.Chandra

Version:

3.7

Keywords:

investigate

Target Milestone:

---

Hardware:

OS:

Mac OS X - Carbon (unsup.)

Whiteboard:

stalebug

Attachments:

Description	Flags
feature projects	none
updated proposed features	none

Description Jeff McAffer

2010-10-21 16:47:19 EDT

Created attachment 181449 [details]
feature projects

Related to Bug 328397, there should be some easy ways for people to add API tools to their releng build setup.  For example, if there were an API tools feature that listed the headless API tools function and perhaps the prereqs (depending on the result of reducing its prereq reach) then users could simply "get API tools with that".

As a start I will attach a proposed feature that just has the API stuff, no prereqs.  We could add pde.core for example as a *require* dependency.  That is if the dependency refactoring does not happen.

Comment 1 Jeff McAffer

2010-10-21 21:20:00 EDT

Created attachment 181459 [details]
updated proposed features

This is a revised set of features just to paint a picture of the direction.  Basically there is an "addon" features apitools.core that can be added on to existing systems that already have the majority of the prereqs.  There is also a stand-alone feature that has most of the stuff that is specific to API tooling in a releng build context.  That feature is not complete in that I did not follow the transitive dependencies.  Rather, I figured we'd see if it is possible to trim some of the dependencies as this would significantly reduce the footprint.

Comment 2 Eclipse Genie

2019-05-11 15:28:08 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 3 Eclipse Genie

2021-05-02 09:43:45 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 4 Eclipse Genie

2023-04-23 11:36:57 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.