[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-vcm-dev] More changes
|
The generic actions were there to support the SimpleAccess API, which has
long ago been agreed to as experimental and marked such. The fact the
actions weren't marked so was just an oversight.
TeamAction isn't strong enough to be API. Its just a grab bag of utility
methods that we found useful to make the generic actions. It was never
'designed', and there is nothing particularly 'deep' in there. You are
free of course to copy any code in there you find of value, subject to the
open source IP rules.
I want to understand what people need in this area. We've done
experimental work that made it into builds as a form of exploration. Since
we've never had any feedback or bug reports on TeamAction, its subclasses,
nor the sync classes, they've never benefitted from any form of community
review. The implication is that the community hasn't found them
interesting enough to discuss, and was much more interested in deep
integration of their provider (which we also find much more compelling).
Note that these classes were always marked experimental, as stated in the
project's readme file.
Kevin
"Bryan Stephenson"
<Bryan.Stephenson@meran To: <platform-vcm-dev@xxxxxxxxxxx>
t.com> cc:
Sent by: Subject: Re: [platform-vcm-dev] More changes
platform-vcm-dev-admin@
eclipse.org
05/07/2002 12:54 PM
Please respond to
platform-vcm-dev
The decision to move all of these classes to the internal package means
that
provider implementers
cannot rely on their continued presence and using "internal" classes is
frowned on from the stand point
of the "Ready for WebSphere Studio" program.
<from Ready for WebSphere Studio >
The use of internal interfaces is discouraged as they are subject to change
without notice. Changes to an internal interface may disrupt or disable
your
plug-in which would trigger support and rework costs for your development
team. Approval will be given based on the pre-test report submitted with
your Ready for WebSphere Studio application. Vendors wishing prior approval
should contact (name and e-mail).
While their functionality is not essential to any provider's
implementation,
they do serve as a reasonable starting point.
I feel that the generic TeamAction super class should remain in the public
API as it provides a good basic set of reusable functionality. Both the
CVS
and examples use TeamAction (and other components). The implication of
this change is that the examples and the Eclipse CVS provider are
"discouraged" in terms of the Ready for WebSphere Studio criteria.
Bryan Stephenson
----- Original Message -----
From: <James_Moody@xxxxxxx>
To: <platform-vcm-dev@xxxxxxxxxxx>
Sent: Tuesday, May 07, 2002 4:32 PM
Subject: [platform-vcm-dev] More changes
> The classes in org.eclipse.team.ui.actions have been moved to
> org.eclipse.team.internal.ui.actions effective tomorrow's integration
> build.
>
> These classes were marked as provisional API, and our rationale for
> making
> them internal is the same as for the sync view.
>
> We may change them upon feedback & review, so having them as internal
> gives
> us greater flexibility to do so.
>
> james
>
>
> _______________________________________________
> platform-vcm-dev mailing list
> platform-vcm-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev
_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev
