Community
Participate
Working Groups
See attachment 118976 [details] from bug 239048 comment 2. The synchronize view and the work will be discussed on this bug as I'd like to leave 239048 for an implementation of the sync API that allows changes to the workspace to be distributed in real-time.
This functionality - as shown in the screencast - is exactly what I wanted for my use case (occasional remote tutoring/help). The only problem is that the code is not available (yet) ;-)
Scott, how do we want to name these bundles? I'm leaning towards org.eclipse.team.ecf.core/ui.
(In reply to comment #2) > Scott, how do we want to name these bundles? I'm leaning towards > org.eclipse.team.ecf.core/ui. > Sure, this seems reasonable.
(In reply to comment #1) > The only problem is that the code is not available (yet) ;-) The code is in CVS now under org.eclipse.ecf/framework/bundles/.
(In reply to comment #3) > (In reply to comment #2) > > Scott, how do we want to name these bundles? I'm leaning towards > > org.eclipse.team.ecf.core/ui. > > > > Sure, this seems reasonable. > Actually, I'm not sure that using the org.eclipse.team namespace is actually OK. Do you (Remy) know this to be OK (by team API convention)? Sorry about the lateness on this thought...I thought of it in the middle of the night :).
(In reply to comment #5) > Actually, I'm not sure that using the org.eclipse.team namespace is actually > OK. Do you (Remy) know this to be OK (by team API convention)? Subversive does this with its org.eclipse.team.svn setup (instead of something like org.eclipse.subversive) and CVS's code is in org.eclipse.team.cvs. Hence, since we're implementing Team's APIs on top of ECF's protocols, I figured org.eclipse.team.ecf is the correct way of doing things.
(In reply to comment #6) > (In reply to comment #5) > > Actually, I'm not sure that using the org.eclipse.team namespace is actually > > OK. Do you (Remy) know this to be OK (by team API convention)? > > Subversive does this with its org.eclipse.team.svn setup (instead of something > like org.eclipse.subversive) and CVS's code is in org.eclipse.team.cvs. Hence, > since we're implementing Team's APIs on top of ECF's protocols, I figured > org.eclipse.team.ecf is the correct way of doing things. > OK. Would you please add these new bundles to the project set files in the org.eclipse.ecf.releng project (extssh and anonymous)?
(In reply to comment #7) > Would you please add these new bundles to the project set files in the > org.eclipse.ecf.releng project (extssh and anonymous)? I believe I've done this already (in addition to updating the map files) when I committed the projects. http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ecf/releng/org.eclipse.ecf.releng/projectSet-anonymous.psf?root=RT_Project&r1=1.11&r2=1.12 Scott, are you seeing evidence that indicates otherwise?
(In reply to comment #8) > (In reply to comment #7) > > Would you please add these new bundles to the project set files in the > > org.eclipse.ecf.releng project (extssh and anonymous)? > > I believe I've done this already (in addition to updating the map files) when I > committed the projects. > > http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ecf/releng/org.eclipse.ecf.releng/projectSet-anonymous.psf?root=RT_Project&r1=1.11&r2=1.12 > > Scott, are you seeing evidence that indicates otherwise? > Nope, got them thanks.
It looks as though the manifest.mf for the org.eclipse.team.ecf.ui plugin has a symbolic name of Bundle-SymbolicName: org.eclipse.ecf.sync.team;singleton:=true I think it probably needs to be changed to org.eclipse.team.ecf.ui Also, to incorporate into build lets change the version number in both o.e.team.* plugins to 1.0.0.qualifier (i.e. add the qualifier).
(In reply to comment #10) > It looks as though the manifest.mf for the org.eclipse.team.ecf.ui plugin has a > symbolic name of > > Bundle-SymbolicName: org.eclipse.ecf.sync.team;singleton:=true > > I think it probably needs to be changed to org.eclipse.team.ecf.ui > > Also, to incorporate into build lets change the version number in both > o.e.team.* plugins to 1.0.0.qualifier (i.e. add the qualifier). Done.
Changing target milestone to 3.0M5.
This is a very nice feature, and something I'm very interested in. Looks great.
Great feature. Thanks for the contribution.
