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

Eugene Kuleshov <eu@md.pp.ru> wrote on 03/15/2006 01:45:46 PM:

> 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:

No, you are already wrong. If you are working locally, and the item you
selected contains this property, then AFTER the branch/tag is made, the
local property is updated. It would then still need to be committed.

> 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)

The property would never go into the target of the copy. Or rather, what
properties do go into the target are just based on the rules of a
Subversion copy. This process does nothing that would alter this. The
property management it does do, happens after the copy.

> >> 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.

You got me. I wanted to make sure this feature was difficult. It had
nothing to do with the constraints that exist. I spent weeks adding the
feature and documenting it just for the hell of 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.

We knew before the feature was implemented that it had to be a hack.
Everyone insisted that it was worth it for the benefits it would provide.
I must confess that I really like the feature now that it exists. Make a
suggestion that shows you spent even two minutes trying to understand the
feature and what the Subversion API's and constraints are and I will
listen.

> > 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.
It doesn't seem like you get it.  You still seem to be hung up on the 
property being set in the tag itself which does not happen.
> >>    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?"
Do they have a common parent?  If so, I do it from the repositories view 
so I can tag all 10 at once.  I then manually edit the tags property for 
the 10 projects.  Otherwise, you can create the tag folder in the 
repositories view and then take the Create Branch/Tag option 10 times. 
Once for each project.  This will update the property automatically, 
although it still needs to be committed.
>    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.
Get it started.  Rough out a patch.  Read the web page again, I think it 
is explained.
>    BTW, you should learn from Subversive plugin. It has really 
> interesting approach to tagging...
If I could get it to work long enough, I might try.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs. 
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org