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

Bug 203536

Summary:	[ui] Admin UI should have more repository management features
Product:	[Eclipse Project] Equinox	Reporter:	Jeff McAffer <jeffmcaffer>
Component:	p2	Assignee:	P2 Inbox <equinox.p2-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	jeffmcaffer, mn, pascal, susan
Version:	3.4	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Jeff McAffer

2007-09-16 10:20:33 EDT

The repository lifecycle has changed such that "adding" a repo to a manager does NOT automatically create the repo.  There is now an explicit create API that takes more information.  Administrators and authors will need to be able to create repos and configure them.  For now just adding them is good.  Eventually we'll need a pluggable way of configuring them.

Comment 1 Susan McCourt

2007-09-24 11:42:37 EDT

per discussion in bug #204301, the creation UI is where repos could be named by the repo producer.  See also bug #203115 which involves defining categories for repos.

Comment 2 Susan McCourt

2007-10-15 15:15:05 EDT

I'm not sure I understand why we need separate API for load and add.

If a user knows of a repo somewhere, and wants to add it to their list of repos, all they know is the URL.  So underneath I need to load the repo, and then add it to the manager.  Would anyone ever want to do these things separately?

For now I will change the UI code to do a load/add when the user adds, but I found the API pretty confusing to have both.

Comment 3 Susan McCourt

2007-10-15 15:21:08 EDT

Now I see that the load does the add.
Another source of confusion was that when ProvisioningUtil was updated to the new repo API, addMetadataRepository was implemented using load, and addArtifactRepository was implemented using create.  I'm assuming load is the right thing to do for both.

Comment 4 Jeff McAffer

2007-10-27 13:13:02 EDT

d'oh, yes, it seems that load would be the best bet for you.  Would it make sense to rephrase the UI add (and perhaps API load) notions here as "open"?  It would be good if there was some level of correspondance so we can avoid some future confusion.  open may not be the best choice (since it implies a close)

Comment 5 Susan McCourt

2007-11-06 16:53:15 EST

I'm generalizing the name of this bug because I noticed this line item on the M4 plan:

"Remove IUs from a repository from the Admin UI".  

I assume Pascal added this line item?
The question is how far are we going with the admin UI as far as repo management features.  If we are removing IU's, are we then going to create them, etc. etc.?

Comment 6 Susan McCourt

2010-01-19 15:27:39 EST

closing this bug.  We have repository creation via PDE and repository tools for other tasks (composites, mirrors, etc.)  This is not in the scope of the admin UI.