Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-vcm-dev] Sync view reusable pieces will become internal

I will let you know about my experiences when I have finished my
implementation :)

But you are definitely right concerning those API change issues, I just had 
to remind me that this Team API 2.0 stuff is still work in progress ...

- Boris


On Tue, 7 May 2002 Kevin_McGuire@xxxxxxx wrote:

> 
> Cool!
> 
> Still, I think the right answer is that we will leave it marked internal,
> then do an API review of it post 2.0.  As a client of it we would really
> appreciate your feedback/participation at that time.
> 
> This is in everyone's benefit.  For example, if we declare it API now, then
> even if you had feedback and requests for improvement, we may not be able
> to act on them due to API compatibility rules.
> 
> Cheers,
> Kevin
> 
> 
> 
> 
>                                                                                                                                       
>                       Boris Pruessmann                                                                                                
>                       <boris+mailinglists.platform-vcm-dev@prue         To:      <platform-vcm-dev@xxxxxxxxxxx>                       
>                       ssmann.org>                                       cc:                                                           
>                       Sent by:                                          Subject: Re: [platform-vcm-dev] Sync view reusable pieces     
>                       platform-vcm-dev-admin@xxxxxxxxxxx                will become internal                                          
>                                                                                                                                       
>                                                                                                                                       
>                       05/07/2002 02:26 PM                                                                                             
>                       Please respond to platform-vcm-dev                                                                              
>                                                                                                                                       
>                                                                                                                                       
> 
> 
> 
> 
> You're right. I started to use them a while ago to provide a
> synchronisation view for my Perforce integration, similar to the cvs one.
> 
> - Boris
> 
> On Tue, 7 May 2002 Kevin_McGuire@xxxxxxx wrote:
> 
> >
> > They will be in 2.0, its just that the API hasn't been ratified through
> > sufficient use and review.  Marking it internal is just part of the
> > contract - we reserve the right to change them as we get feedback on
> usage.
> >
> > Actually, we didn't think anyone was using it.  I take it you are?
> >
> > Kevin
> >
> >
> >
> >
> >
> 
> >                       Boris Pruessmann
> 
> >                       <boris+mailinglists.platform-vcm-dev@prue
> To:      <platform-vcm-dev@xxxxxxxxxxx>
> >                       ssmann.org>
> cc:
> >                       Sent by:
> Subject: Re: [platform-vcm-dev] Sync view reusable pieces
> >                       platform-vcm-dev-admin@xxxxxxxxxxx
> will become internal
> >
> 
> >
> 
> >                       05/07/2002 02:39 AM
> 
> >                       Please respond to platform-vcm-dev
> 
> >
> 
> >
> 
> >
> >
> >
> >
> >
> > Will they stay there until R2.0?
> >
> >
> > On Mon, 6 May 2002 James_Moody@xxxxxxx wrote:
> >
> > > The types in org.eclipse.team.ui.sync will be moved to
> > > org.eclipse.team.internal.ui.sync in the next Integration build. We
> have
> > > not yet decided on what shape, if any, the reusable sync view parts
> will
> > > take, and for this reason we have elected to make them non-API.
> > >
> > > Sorry for any inconvenience,
> > >
> > > james
> > >
> > >
> > > _______________________________________________
> > > platform-vcm-dev mailing list
> > > platform-vcm-dev@xxxxxxxxxxx
> > > http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev
> > >
> > >
> >
> > --
> > "Engineering does not require science. Science helps a lot but
> > people built perfectly good brick walls long before they knew why
> > cement works." - Alan Cox
> >
> >
> > _______________________________________________
> > 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
> >
> >
> 
> --
> "Engineering does not require science. Science helps a lot but
> people built perfectly good brick walls long before they knew why
> cement works." - Alan Cox
> 
> 
> _______________________________________________
> 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
> 
> 

-- 
"Engineering does not require science. Science helps a lot but 
people built perfectly good brick walls long before they knew why 
cement works." - Alan Cox




Back to the top