Re: [Subclipse-users] Multiple subclipse versions co-exist in same development team using same repository?

On Fri, Sep 4, 2009 at 10:05 AM, Jacob W<progsub_at_hotmail.com> wrote:

> We have a development team using the same 1.2.x version of subclipse.  Some of us would like to try
> out the new features in 1.6.x but not sure if there will be a impact to others due to difference in working
> copy format?

The working copy format is confined to a single developer's working
copy. One does not effect another. Heck, if you are careful a single
developer can even use multiple copies of Eclipse/Subclipse on the
same system. You just have to keep your working copies separate.
None of this has any impact on the repository or anyone else's usage
of SVN.

> I've more questions and hope someone could help:
>
> 1) If a developer commits code with subclipse 1.6.x, can another developer using subclipse 1.2.x (in
> another Eclipse workspace) checks out/changes/commits to the same SVN repository & vice versa?

Absolutely. Just think of all the large open-source projects that use
SVN. Do you think they make any effort to have users using the same
SVN clients or even client versions?

> 2) Does subclipse check in any .svn directory content or any metadata to SVN repository? e.g. working
> copy format

No. The metadata is just used by SVN to track what is in your working copy.

> 3) If I upgrade to subclipse 1.6.x and then want to switch back to 1.2.x, is it as simple as creating a new
> Eclipse workspace, install subclipse 1.2.x and check out the code again?  Or should I just use the old
> workspace but delete all the .svn directories?

Yes, this will work fine.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2391028
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].