RE: [platform-vcm-dev] Team 2.0 work going to builds, but plugins are t

["Clemm, Geoff" <gclemm@xxxxxxxxxxxx>]

Kevin:

That's great news!  Of course, as soon as you give us something, you
get asked for more (:-) ... in particular:

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]
Sent: Tuesday, January 15, 2002 5:47 PM
To: platform-vcm-dev@xxxxxxxxxxx
Subject: [platform-vcm-dev] Team 2.0 work going to builds, but plugins
are turned off


As part of our progression towards general availability of the Team 2.0 
work, we are "practicing" contributing to the builds. 

This is *not* an announcement of its availability for people to use in day 
to day development. Rather, its a test of our contribution to the build 
process, and a way to provide baselines for people to develop 
against. Finally, this announcement is being sent so people are not 
surprised by the appearance of the plugins.

This is true as of today's build (20020115).

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

In order to prevent the appearance of two "Team" menus, we've turned off 
our two team UI plugins by naming them plugin.xml.off.

To get the plugins working, copy the following two files:

1.      Rename plugins/org.eclipse.team.ui/plugin.xml.off to 
plugins/org.eclipse.team.ui/plugin.xml 
2.      Rename plugins/org.eclipse.team.cvs.ui/plugin.xml.off to 
plugins/org.eclipse.team.cvs.ui/plugin.xml 

The Team Team
_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev