Home » Eclipse Projects » Subversive » feature request: tagging with current position in the tree
| feature request: tagging with current position in the tree [message #22242] |
Thu, 26 June 2008 08:29  |
 Michele Zamparelli
Messages: 2
Registered: July 2009 |
Junior Member |
|
|
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
|
|
|
| Re: feature request: tagging with current position in the tree [message #22282 is a reply to message #22242] |
Thu, 26 June 2008 11:06  |
David Pérez
Messages: 228
Registered: July 2009 |
Senior Member |
|
|
Hi,
I have upgraded from Eclipse 3.3 to Eclipse 3.4. We used to use before
org.tigris.subversion.subclipse.core_1.2.4.
Subversive included with Ganymede works ok (I can synchronize, ....), but
I'm unable to tag any project. Before I didn't have any problem.
In the tag dialog, when I press the "Browse" button, I see this error
message "An occurred while accessing the repository entry".
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
|
|
| |
| Re: Tagging doesn't work in Ganymede [message #22720 is a reply to message #22676] |
Fri, 27 June 2008 11:35 |
Eclipse User |
|
|
|
Originally posted by: alexander.gurov.polarion.org
Hello David,
It looks like you have no tags folder created. Is it possible or not? If
so, you have set of options which allows to avoid the problem:
1) You can enter tag name manually (and tags folder will be created
automatically)
2) You can create tags folder manually (in that case "Browse" button will
not show any tags until tags are created)
3) You can disable support of SVN recommended layouts at
Window->Preferences->Team->SVN->Repository->Branch and Tag Settings and in
that case "Browse" buttoon will simply show repository content instead of
tags folder content.
|
|
|
| Re: feature request: tagging with current position in the tree [message #22849 is a reply to message #22242] |
Fri, 27 June 2008 13:10 |
| Eclipse User |
|
|
|
Originally posted by: alexander.gurov.polarion.org
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
|
|
| | |
| Re: feature request: tagging with current position in the tree [message #23669 is a reply to message #23068] |
Wed, 02 July 2008 13:37 |
| Eclipse User |
|
|
|
Originally posted by: alexander.gurov.polarion.org
Hello Michele,
> But it is not true what you write, that our projects are not contained
> inside the trunk node, because they are. The difference with the customary
> approach which is supported by your plugin, is merely that instead of
> having one unique flat namespace, we prefer to use a hierarchy, as it is
> customary for instance with CVS projects.
Yes, I understand that in your case projects are placed somewhere under
"trunk" node. But how we can determine on which hierarchy level a project
is started? The only one way I see is: sequentially enumerate all children
until ".project" file is found. This way takes too much time and will not
be used in any case. And this mean that handling of the repository
structure used in your team cannot be automated, instead you can specify
tag names with all required path members manually, for example:
tag_27.03.2008/f1/f2
|
|
|
Goto Forum:
Current Time: Thu Dec 26 17:03:55 GMT 2024
Powered by FUDForum. Page generated in 0.03969 seconds |
] 
Search
Help
Register
Login
Home
