However, VSS has the following benefits:
- It is integrated into Visual Studio
- It does not slam the performance of my code directories.
Both of those 'features' may convince me to switch back.
Kevin
>>> dan@tastapod.com 8/12/2004 4:46:39 AM >>>
Amen to that! VSS? Ouch.
Rob Jose wrote:
> Hi Dan
> You are correct. I didn't mean to imply that I was upset or
> anything. I am sorry if I did. I just wanted to make sure that it
> wasn't available. My boss keeps telling me that he went to a demo of
> subclipse and they did branching and switching right from the IDE. I
> keep telling him that it is not there. I just wanted validation that
> the feature is indeed not there. I hate it when I tell my boss
> something isn't there when it is right in front of my face :). Now
to
> write up the documentation for doing this so I can get us off of
VSS.
>
> Rob
>
>
> ----- Original Message -----
> *From:* Dan North <mailto:dan@tastapod.com>
> *To:* users@subclipse.tigris.org <mailto:users@subclipse.tigris.org>
> *Sent:* Wednesday, August 11, 2004 9:17 AM
> *Subject:* Re: svn switch and checking out to an external working
folder
>
> Hi Rob.
>
> I tend to view things as either day-to-day development activities or
> less frequent "project admin" activities. As long as my IDE supports
> the former, then I'm happy.
>
> So for creating a branch (svn copy followed by svn switch --relocate
> or a fresh checkout) and then syncing to the branch (create a new
> project over the branch directory) I'm happy to do that from the
> command line. For regular activities such as refactor->rename (svn
> move to delete/add-with-history), add new files, commit, etc. I want
> my IDE to do this, and to do it as transparently and unobtrusively as
> possible.
>
> It seems to me that the subclipse developers have hit this balance
> exactly right. They are focusing (a lot of) effort into making the
> day-to-day stuff as simple as it can be, and using any spare cycles
to
> integrate the less common stuff (such as viewing history - since
> Eclipse already has a great local history feature).
>
> In the meantime, I'm happy to use the command line to do the less
> frequent stuff. Especially since it always seems to be slightly
> different each time I do it, which is a hint to me that automating it
> by means of an Eclipse wizard would be quite a difficult undertaking
> anyway.
>
> Of course, ymmv.
>
> Cheers,
> Dan
>
> Rob Jose wrote:
>
>> Ian
>> Thanks for your response. I was thinking that Subclipse hadn't
>> developed this functionality yet, I just wanted to make sure.
Thanks
>> again for your help.
>>
>> Rob
>> ----- Original Message -----
>> *From:* Ian Brockbank <mailto:Ian.Brockbank@wolfsonmicro.com>
>> *To:* users@subclipse.tigris.org
<mailto:users@subclipse.tigris.org>
>> *Sent:* Wednesday, August 11, 2004 1:44 AM
>> *Subject:* RE: Re: svn switch and checking out to an external
working
>> folder
>>
>> Hi Rob,
>>
>> 1) After I branch, I can not figure out how to switch my project to
>> use the new branch. For example, I have a plugin called
>> Administrator. I have branched it to another location so I can do
>> some changes without bothering anyone else. I noticed that
>> subversion has a command called switch that will point my working
>> directory to the branch. Does subclipse have the capability to do
>> this? If not, what are other doing in this situation?
>>
>> You could always try the command line - svn switch. Type "svn help
>> switch" for more info.
>>
>> True, I could use the command line, but shouldn't subclipse have the
>> option someplace. I would think that subclipse would be able to do
>> all of the commands that you can do from the command line. What I
>> would really like to do is to do a branch from subclipse, and then
>> tell subclipse to update from the branch instead of updating from
the
>> trunk. Does this make since? Maybe I am too use to VSS and what I
>> am saying is not the correct work flow. If that is the case, can
>> someone tell me what the correct work flow is?
>>
>> Remember Subversion v 1.0 was only released in February, and Eclipse
>> 3.0 was only released in June. The team has been making great
>> progress in the last few months since the Eclipse 3.0 Teamwork API
>> was sufficiently documented for them to be able to make progress
>> again. I'm sure it's only a matter of time before it's implemented
>> in Subclipse - they've probably taken note of your request, but you
>> can submit a feature request via the web site to make sure. Until
>> then, there's always the command line. Alternatively, this is an
>> open source project, so you're welcome to have a go at implementing
>> it yourself and to submit a patch for the core development team to
>> review and (hopefully) commit.
>>
>> Cheers,
>>
>> Ian Brockbank
>> Senior Applications Software Engineer
>> e: ian.brockbank@wolfsonmicro.com /* apps@wolfsonmicro.com
>> *scd: ian@scottishdance.net
>> t: +44 131 272 7145
>> f: +44 131 272 7001
>>
>
Received on Fri Aug 13 03:56:03 2004