[news.eclipse.technology.subversive] Re: feature request: tagging with c

[alexander.gurov@xxxxxxxxxxxx (Alexander Gurov)]

Hello Michele,


Because Subversion provides no support for branches and tags (instead 
Subversion supposes that branches and tags are a folders which contain 
resource copies) we have written some heuristic code which detects used 
repository layout and then provides all required automation. In your 
situation you have non-standard layout (your projects is not contained 
inside the trunk node), and in order to provide some automation we should 
write much more of heuristic code. But too much of heuristic code is not a 
good solution, because this code could contain many hidden issues. So, I 
think we should not change plug-in in order to automate rare workflows.

> From the other side you always can specify right tag or branch name, for 
example type in "Tag name" field "Integration20080618/alpha/beta/M1" and 
you will have required structure on repository after pressing "Ok" button. 
:)

Michele Zamparelli wrote:

> Dear Subversive folks:

> I have the following problem, maybe you can help me.
> We use the word "module" to identify a well defined directory structure 
> like:

> M/src
> M/include
> M/object/
> M/lib


> Suppose that M1 and M2 are two modules in the tree-like SVN repository, 
> which could look like:

> trunk/alpha/beta/M1   assigned to person P1
> trunk/alpha/beta/M2   assigned to person P2

> Our developers are using Eclipse with the Subversive plugin.

> Suppose P1 wants to tag M1 with the name "MyTag" (or any other symbolic 
> name, for that matter).
> M1 is normally handled as a single "project" in Eclipse.

> Subversive only allows the following tag to be created:

> tags/Integration20080618/M1       whereas what would be desired is:
> tags/Integration20080618/alpha/beta/M1

> In other words in our community it is fairly important that when a 
> symbolic name is communicated, the user of such release can extract the 
> code from the repository and find it in the customary location, i.e. 
> according to the tree structure which is present in the trunk.

> Notice that such a behavior can be achieved with the command line, 
> although in an error-prone way, by doing something like:
> svn mkdir -m "creating tag MyTag" svn://URL/tags/Mytag
> svn mkdir -m "creating tag MyTag" svn://URL/tags/MyTag/alpha
> svn mkdir -m "creating tag MyTag" svn://URL/tags/MyTag/alpha/beta
> and finally
> svn copy  -m "taggin MyTag" M1 svn://URL/tags/MyTag/alpha/beta

> I have played with the different Repository Layout options (Single Project 
> Layout, Multiple Project Layout, Monolithic Project Layout) but this does 
> not seem to have an impact on my issue.
> Am I missing any configuration option?

> Could the Subversive plugin be modified in this direction? (i.e. an option 
> would offer to create the missing alpha/beta pieces under the tag).
> Does it make sense in the first place?

> I am kind of lost at this stage, so any kind of help is greatly 
> appreciated.

> Michele