Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 266070 - [publisher] Make update site actions API consistent
Summary: [publisher] Make update site actions API consistent
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Ian Bull CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-24 23:53 EST by Ian Bull CLA
Modified: 2019-09-30 11:59 EDT (History)
0 users

See Also:

Attachments
patch (2.93 KB, patch)
2010-02-15 17:50 EST, Ian Bull CLA 		no flags Details | Diff
View All 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 Ian Bull CLA 2009-02-24 23:53:19 EST 
With Bug 264389, the different update site actions have inconsistent API in their constructor.  We should look to make this consistent.
Comment 1 Ian Bull CLA 2009-04-28 13:39:05 EDT 
We should look at htis when we do our API review in 3.6
Comment 2 Ian Bull CLA 2009-06-09 23:49:33 EDT 
If we are going to add or change API, let's do this early.
Comment 3 John Arthorne CLA 2009-09-16 13:46:36 EDT 
Ian, I'm bumping these again to M3, but please review these bugs and pick a reasonable target (or remove the target if you have no immediate plans to work on them).
Comment 4 Ian Bull CLA 2009-10-30 12:05:08 EDT 
This will be going in the API branch and be available in M4.
Comment 5 Ian Bull CLA 2010-02-15 17:50:12 EST 
Created attachment 159132 [details]
patch

Here is a first attempt at making the remote and local update site actions consistent. We still need some test cases though.
Comment 6 Ian Bull CLA 2010-04-16 15:21:02 EDT 
bumping to 3.7.
Comment 7 Eclipse Genie CLA 2019-09-30 11:59:29 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.