Community
Participate
Working Groups
Build ID: M20080221-1800 Steps To Reproduce: 1. Switch to any perspective other than "SVN Repository Exploring" perspective, for example "Resource" perspective. Create a new branch, for example "svn://localhost/justanothersample/branches/mybranch". Switch to the new branch. 2. From "Resource" perspective invoke "Team -> Tag..." command. In "Create Tag" dialog specify new tag location, for example "svn://localhost/justanothersample/tags/mybranch_tags/myfirsttag". Click OK. 3. New tag is created with an extra redundant "original resource name" as last segment, for example "svn://localhost/justanothersample/tags/mybranch_tags/myfirsttag/mybranch". More information: Above description is compiled with "Branch and Tag Settings" switched to "Manual specification". However, same can be experienced with "Respect project structure" option enabled, when one use "/" inside tag names as in "mybranch_tags/myfirsttag". Workaround is to work from "SVN Repository Exploring" perspective where tags from branches are created as expected, without redundant suffix. Above workaround will not cover tagging from working copy with mixed revisions, which is quite unfortunate. I've already filed this bug under ID# 229007, but for some reason it is not shown in search results. Therefore, I'm submitting it here again (I'll mark 229007 as duplicate of this one).
*** Bug 229007 has been marked as a duplicate of this bug. ***
Now all perspectives behaves identically (fix will be available at the end of this week). Behaviour rules are: - no structure -> copy content to destination - structure detection disabled -> copy selection content to destination - consider structure disabled -> copy selection content to destination - single-project layout:trunk selected -> copy selection content to destination - single-project layout:child of trunk selected -> copy selection content to destination - multiple-project layout:trunk selected -> copy selection content to destination - multiple-project layout:trunk children selected -> copy selection to destination - multiple-project layout:one child of trunk selected -> copy selection to destination - tagging from branch and branching from tag uses the same rules, i.e. respects a project layout. In order to track future improvements of branching and tagging you can subscribe to: 223871: Improve Branching and Tagging https://bugs.eclipse.org/bugs/show_bug.cgi?id=223871
(In reply to comment #2) This is great:-) Can't wait to try it out. Many thanks. Best regards, Damir Murat
