[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] What is Tags column on Resource History used for?

From: Eugene Kuleshov <eu_at_md.pp.ru>
Date: 2006-03-15 19:45:46 CET

Mark Phippard wrote:

>> others in this forum not to create tags/branches from working copy
>> because it may have local changes.
> You can run the Create Tag option from the WC but create it against the
> URL. Plus, there are times when you want it to include the local changes.
> The bottom line on this is to just do whatever the right thing is. Only
> you can know that.

   I see. So, now I can choose to make a copy from trunk in tag/branch
dialog and according to you this dialog will update tag property prior
copying to target folder? I can understand what is happening there, but
it is not quite transparent. Please correct me if my guesses are wrong:

1) If I choose "HEAD revision in repository" in tag/branch dialog, then
tag property will not go into target cop, unless I manually create it
before calling tag/branch dialog

2) If I choose "Working copy" in tag/branch dialog, then property will
be created locally, but not committed and will also go into target copy.

   This is what I'd like to see documented. More over I'd prefer that
property would be committed to head for me before doing copy in case 1)

>> Also it does not work when you need
>> to tag multiple projects. Look at Subversion's own project structure as
>> an example. It is not that uncommon when you have to tag 3 to 10
>> projects when releasing new version of Eclipse plugin. How Subclipse is
>> helping with that?
> It doesn't and can't. So what?

   That is where we disagree. It could, but you didn't want it.

> Should we have not added the feature? Is
> it that hard to manually manage the property?

   It is easy for single project, but annoying and time consuming and
error prone when you have to do it for 10 projects. Besides, it is easy
to forget to do so. This is not really IDE-friendly behavior.

> What don't you get here? The property is not set on the tagged copy --
> EVER. It is set on the SOURCE of the tagged copy. If you make a tag from
> trunk, then trunk needs the property, not the tag.

   I perfectly get everything. What you don't get is that such common
scenario is really purely explained in documentation.

>> I think it is quite common use case that been asked several times in
>> this mail list. I'd say it is worth a FAQ entry...
> I do not know what would be an FAQ entry, and this is one of the first
> conversations I can ever remember happening since this feature was
> implemented. Hardly anyone has ever even mentioned the feature, despite
> several people begging for it for months.

   Question to answer is this: "I have working set of 10 projects that
need to be tagged/branched at the same time. How do I do that in Subclipse?"

   Also, I may not understand how that property is working, but from
what I've seen, tag/branch copy has been created and then tag info
property is changed/added into head revision. Kind of strange to do such
thing in head revision after tagging. This kind of behavior is not
explained anywhere in Subclipse documentation and I am basically asking
to fix that.

   BTW, you should learn from Subversive plugin. It has really
interesting approach to tagging...


To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Mar 15 19:46:36 2006

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.