Eugene Kuleshov <email@example.com> wrote on 03/15/2006 12:32:48 PM:
> Mark Phippard wrote:
> >> That is what I am asking for. How do I create a branch in a way
> >> this property will be auto maintained.
> > Right-click on a Project in your WC that has the subclipse:tags
> > set and choose Create Branch/Tag.
> > That is the only time it can be done. Otherwise, you need to set the
> > property manually.
> I knew you'd suggest that. From other hand, I've been told by you and
> 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.
> 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? Should we have not added the feature? Is
it that hard to manually manage the property?
> >> Last time I asked about branches here , I've been suggested to go
> >> repositories view and basically do copy from trunk folder and paste
> >> branch/tag folder. If I do that nothing created automatically.
> > You cannot set a property against a URL. I also make tags this way. I
> > then manually update the projects that I tagged to set the property.
> Right. But then this property won't appear under working copy checked
> out from branch or tag. Note that tagged copy not supposed to be changed
> and that could be enforced on server.
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.
> > There is never a scenario where it will be propogated to the target
> > branch. What will be propogated is any properties that existed when
> > branch was created, and that is all that it makes sense to propogate.
> Am I that bad in explaining what am I looking for? Or you just
> pretending that you don't want to understand what I am asking?
I think you just do not understand the feature correctly, or you would not
be asking this. I have answered it correctly each time. The property is
not set in the target -- EVER.
> 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.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Mar 15 19:08:40 2006