Re: [platform-vcm-dev] Recommended way of using *internal* packages such

["Michael Valenta" <Michael_Valenta@xxxxxxxxxx>]

Greg,

We do not anticipate changing any of these classes in any future 2.X releases. We are currently working on an improved syncing story for 3.0 that will make it easier for team providers (and users) to use. This work is being done in separate packages and will not effect the current sync view implementation. For more details, please see the VCM Component 3.0 plan:

http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/docs/online/team3.0/milestone-plan.html

Michael

Greg Kim <gkim@xxxxxxxxxxxxxx> Sent by: platform-vcm-dev-admin@xxxxxxxxxxx 20/05/2003 10:31 PM Please respond to platform-vcm-dev

To:        "'platform-vcm-dev@xxxxxxxxxxx'" <platform-vcm-dev@xxxxxxxxxxx>         cc:                 Subject:        [platform-vcm-dev] Recommended way of using *internal* packages such as SyncView?

I created a Team Repository plugin to work with Eclipse 2.0x sometime
last year and haven't touched it until now. I've verified that my plugin
still works w/ 2.02, but I'm running into a compatibility problem on 
2.1. 

The problem is the following: 
  org.eclipse.team.internal.ui.sync.SyncView

The method signature of findInActivePerspective(void) appears to 
have been changed to findViewInActivePage(IWorkbenchPage). Yes, 
this is one of those 'internal' classes, so it was just a matter
of time I guess...  

I'm reusing lots of stuff in the org.eclipse.team.internal.ui.sync
package which is experimental and likely to change in the not 
so far future.  In order to protect myself from compatibility 
issues moving forward, I'm thinking about basically copying all
the ui.sync classes into my plugin.   And switch back once this
package becomes stable...     

Anyone (especially Team Repository plugin builders, since there 
appears to be more need for 'internal' classes) experiencing compatibility
grief such as these?

I ideally want to ship one plugin package that works on 2.x 
(i.e. 2.02, 2.1, 2....).
Is there a better way of doing this?

I'm also extending from TeamAction (another *internal* class) to 
handle all my Team actions.  Is there going to be a change to
this interface before 3.0?

Appreciate all the help,
thanks!
Greg

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