[platform-vcm-dev] RE: separating out "team.kickstart" from "team.core"

[gclemm@xxxxxxxxxxxx]

Kevin:

Has your team had a chance to make this pass through team.core
and team.gui to identify the pieces that will be extracted
into a separate "team.kickstart" plugin?  Even just a rough list
of the pieces would give us a chance to verify that we are
in synch with what you are planning.

Thanks,
Geoff


-----Original Message-----
From: Kevin_McGuire@xxxxxxx [mailto:Kevin_McGuire@xxxxxxx]
Sent: Thursday, January 17, 2002 11:36 AM
To: platform-vcm-dev@xxxxxxxxxxx
Subject: RE: [platform-vcm-dev] Team 2.0 work going to builds, but
plugins are turned off


Hi Geoff,

Yes, this change is still planned.  We were holding off on it because we 
didn't want to destabilize an important customer that was trying to get a 
prototype done.

We hope to propose the required changes to the community within the next 
week or so.

Thanks for the feedback,
Kevin



From: "Clemm, Geoff" <gclemm@xxxxxxxxxxxx>

In an earlier thread, we discussed separating the Team plugin into
three pieces:

- the "team.core/team.gui" plugins.  These plugins define
  routines/extension-points (e.g. ValidateEdit, ValidateSave,
  decoration support, associate project with CM provider, CM menu
  insertion locations) that must be provided by all Team
  providers.  Also, all editors must invoke the appropriate routines
  (such as ValidateEdit) if they care about Team behavior.

- the "team.kickstart.core/team.kickstart.gui" plugins (I just made up
  those names :-).  These plugins allow rapid implementation of a
  simple team provider, by providing a set of generic CM GUI code that
  invokes a set of specified headless simple-cm API functions (manage,
  get, checkout, checkin, etc.).  A simple Team provider can be
  implemented by combining the team.kickstart plugins with a
  repository plugin that implements the simple-cm API.  *Only* the
  team.kickstart plugin (or a team provider plugin that uses the
  team.kickstart plugin) should call the simple-cm API.  For example
  any non-team plugin (such as an editor) MUST NOT call the simple-cm
  API because it will not in general be provided by a Team provider).

- the "team.cvs.core/team.cvs.gui" plugins.  These plugins define a
  CVS team provider, based on (I believe) the team.kickstart
  functionality.

It appears that the separation into team and team.kickstart has
not yet occurred.  For example, org.eclipse.team.core contains
ITeamProvider.java, which combines both core functionality
(e.g. ValidateEdit, ValidateSave) with kickstart functionality
(the simple-CM API).  Another example is org.eclipse.team.ui.actions,
which contains both "team" functionality (DeconfigureProjectAction.java)
and "team.kickstart" functionality (CheckinAction.java).

I mostly want to confirm that separating the "team.kickstart" plugins
from the "team" plugins is still the plan of record.  Assuming
that is so, the earlier that this split is made, the sooner we can 
confirm:

- our editors are only calling the team plugin functionality (and
  not team.kickstart functionality)

- our CM provider is implementing the full team plugin functionality
 (i.e. we have not misunderstood the division between "team" and
 "team.kickstart").

Thanks!

Geoff


-----Original Message-----
From: Kevin_McGuire@xxxxxxx [mailto:Kevin_McGuire@xxxxxxx]

For those who are interested in the work, you will see the following 
plugins:
        org.eclipse.team.core
        org.eclipse.team.ui
        org.eclipse.team.cvs.ssh
        org.eclipse.team.cvs.core
        org.eclipse.team.cvs.ui