RE: [Subclipse-users] Subclipse 1.1.6 - change sets, synch

Sorry if I wasn't clear.

I am using 3.2, so I'm not sure if you mean that Subclipse needs to take
advantage of the Eclipse feature or not.

As for the version number, way back when Subclipse used to update to the
revision number that the sync was done to, so that if you did a Team
Sync, and someone checked in another commit before your update, you
wouldn't get the latest. Moreover, if you did a sync, a commit, and then
an update (wrong procedure, I know), you'd end up rolling back your
changes locally (although they'd still be in the repository). This was
changed several versions back so that update always pulled from HEAD, no
matter when the sync was done.

Subclipse now seems to have reverted back to the old behavior of syncing
to a given revision number. This is probably because of the change sets,
but I did prefer the previous behavior.

                jason

-----Original Message-----
From: Mark Phippard [mailto:markp@softlanding.com]
Sent: Thursday, September 21, 2006 12:07 PM
To: users@subclipse.tigris.org
Subject: Re: [Subclipse-users] Subclipse 1.1.6 - change sets, synch

"Bennett, Jason" <JBennett@MainPointSystems.com> wrote on 09/21/2006
03:02:17 PM:

> Is the change set feature supposed to work in Incoming/Outgoing mode,
as

> opposed to one or the other? I can see it work when I select either
one,
but
> since I usually work in the union view, it doesn?t seem to work there.

It only shows in one or the other. This feature is set by the view, not

us. In 3.2, CVS is using a new technique which is why I think they now
offer it in both modes. In 3.1, it was the same as this.

> The out-of-date folders feature also seems a little flaky. I just
turned
on
> refresh on build to try and eliminate those folders getting left over,

but I
> see that subclipse is again synching to a given version number
(instead
of
> HEAD), which I believe was changed a few versions ago. The synch view
also
> doesn?t always update, sometimes showing me 2 of the same project
folders in
> the view, or not refreshing the folders properly.

Showing the project folder twice is an Eclipse bug that has been fixed
for
3.2.1 release. Didn't really understand any of the rest.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Sep 22 20:25:52 2006