Mark Phippard wrote:
>> That is what I am asking for. How do I create a branch in a way that
>> this property will be auto maintained.
> Right-click on a Project in your WC that has the subclipse:tags property
> 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. 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?
>> Last time I asked about branches here , I've been suggested to go to
>> repositories view and basically do copy from trunk folder and paste to
>> 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.
>> So, once again, can you please publish step by step instructions how
>> to branch multiple projects and to make sure that this property get
>> propagated to the target tag/branch.
> There is never a scenario where it will be propogated to the target
> branch. What will be propogated is any properties that existed when the
> 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 it is quite common use case that been asked several times in
this mail list. I'd say it is worth a FAQ entry...
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Mar 15 18:33:16 2006