[Subclipse-users] Multiple subclipse versions co-exist in same development team using same repository?
From: Jacob W <progsub_at_hotmail.com>
Date: Fri, 4 Sep 2009 07:05:21 -0700 (PDT)
Hi,
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?
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?
2) Does subclipse check in any .svn directory content or any metadata to SVN repository? e.g. working copy format
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?
I've tried reading Mark Phippard postings on the impact to working copy upgrade, but still not 100% sure about the above.
TIA.
Jac
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
|
This is an archived mail posted to the Subclipse Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.