[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-team-dev] Fw: Team API Usage Question
|
Not sure if I should have made this more explicit, but the nature of the
RCP application is not restricted to version control, it just happens to
be an integral component. The primary function of the application is to
provide an editing framework for managing domain specific metadata of
course, must be versioned and maintained in a remote repository.
-----Original Message-----
From: Paul Wuethrich
Sent: Friday, February 20, 2004 2:35 PM
To: platform-team-dev@xxxxxxxxxxx
Cc: Michael_Valenta@xxxxxxx
Subject: [platform-team-dev] Fw: Team API Usage Question
Per Michael's suggestion below, I'm continuing the discussion.
The 3rd party requirements are virtually non-existent in this case and
the repository provider will be our own customized interface to an
rdbms. I'm guessing this doesn't change the suggested approach of
building it from scratch?
"Michael Valenta" <Michael_Valenta@xxxxxxx> wrote in message
news:<40367918.3080005@xxxxxxx>...
> Paul,
>
> The Team plugin (org.eclipse.team.core) is dependant on the resources
> plugin (org.eclipse.core.resources) so any RCP app that used team
would
> need to be IResource based at least for the resources under version
> control. Including the UI portion has further dependencies (i.e. you'd
> end up with most of the platform SDK plugins).
>
> Also, there is no Team API that allows third party tools to invoke
> repository funtionality. The API is really there to provide
integration
> points for repository providers. If you plan on using a particular
> repository type (e.g. CVS) you may want to investigate developing a
> small client that does only what you need.
>
> If you want to discuss this further, the platform-team-dev mailing
> list
> may be a better place.
>
> Michael
>
> Paul Wuethrich wrote:
>
> > The requirements are to provide team-like functionality to an RCP
> > application for version control over a small set of domain specific
> > files. The end-users will be "business" users and so a full blown
> > CVS implementation is not required.
> >
> > The current plan is to extend the Team api. Is there any reason NOT
> > to use the Team plugins and build the versioning functionality from
> > the ground up? I'm guessing not but I have limited experience in
> > this area and have used the CVS client and experimented with the
> > file system example.
> >
> >
> >
>
_______________________________________________
platform-team-dev mailing list
platform-team-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-team-dev
