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

Bug 37705

Summary:	[plan item] Improve team API
Product:	[Eclipse Project] Platform	Reporter:	Jim des Rivieres <jeem>
Component:	Team	Assignee:	Platform Team Inbox <platform-team-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P4	CC:	balask, champion, crivet, danjou, danrubel, dave.screen, dj.houghton, ekuleshov, geoffrey.clemm, gunnar, jgossage, kratky, m.a.r.k, Michael.Valenta, nikolaymetchev, pombredanne
Version:	2.1	Keywords:	plan
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	146917, 188849

Description Jim des Rivieres

2003-05-15 11:30:48 EDT

Improve team API. Since Eclipse 2.0, each team repository provider adds its 
own specialized commands to the Eclipse UI. There are no common APIs for a 
plug-in tool to programmatically interact with different team providers. JSR-
147 is in the process of developing common API for creating and manipulating 
sets of version-controlled files and web resources, based on the DeltaV 
extension to WebDAV. Eclipse should support this experimental API. [Platform 
Team]

Comment 1 Jean-Michel Lemieux

2003-10-03 09:51:28 EDT

We have written a document explaining how we plan to address this 3.0 work 
item. Please have a read and post comments to the vcm mailing list or to this 
bug report. As stated in the document, this work will begin in the M5 
milestone.

http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-
home/docs/online/team3.0/team_api.html

Comment 2 Gunnar Wagenknecht

2004-01-29 02:23:29 EST

Will there be support for sharing one project in multiple repositories?

Comment 3 Jean-Michel Lemieux

2004-01-29 09:38:57 EST

We have finished our priliminary evaluation of JSR 147 (WVCM).  We have always 
been interested in WVCM because it has industry backing and is a very 
comprehensive abstraction for modern versioning system capabilities. Although 
it would be a good candidate for a Repository Provider API in Eclipse Team, at 
this time the JSR is still under public review with a deadline of mid winter 
2004 and a reference implementation is not yet available. This, combined with 
the lack of documentation and examples, has lead us to the conclusion that we 
cannot release an Eclipse Team API in 3.0 based on a JSR that is still under 
review and not yet final. As a result we are deferring the Improve Team API 
plan item until after 3.0.

Comment 4 Daniel Florey

2004-02-17 06:47:43 EST

Have a look at
http://jakarta.apache.org/slide
In the cvs head (not included in the 2.0 beta1) there is a reference
implementation for jsr-147. Slide is currently not supporting advanced
deltaV-features but it could be a good starting point for investigating wvcm.
Eclipse integration would be great as subversion will be released soon as well.

Comment 5 Jean-Michel Lemieux

2004-06-11 16:51:56 EDT

Post 3.0

Comment 6 Michael Valenta

2005-01-13 11:12:48 EST

*** Bug 82672 has been marked as a duplicate of this bug. ***

Comment 7 Michael Valenta

2006-06-14 09:24:18 EDT

There is currently no plan to address this item.

Comment 8 Denis Roy

2009-08-30 02:16:13 EDT

As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.