use svn:externals property value to include secondary repository in project
When you have a repository with another repository inside (with the svn:externals property) all the changes inside this repository should also be tracked by redmine.
In the current behavior we would have to add the second repository as a subproject to be able to see the commit messages, to brows through the source tree and to automatically close issues with the "fixes" keyword in my commits.
This issue is related to issue #1581 but it should not just display the property value, instead redmine should use that information to also track that repository within the same code tree and within the same project.
#2 Updated by Deniz Bahadir almost 10 years ago
+1 for implementing this feature.
axaris software & systeme GmbH wrote:
Is this to complicated?
It would be nice to know if it is a difficult task (or requires some other features to be implemented beforehand)? Or is it just lack of time, because of so many other features to implement?
#3 Updated by Etienne Massip almost 10 years ago
#4 Updated by Deniz Bahadir almost 10 years ago
Etienne Massip wrote:
I will try to explain, what my concern is:
SVN-externals are similar to symlinks. They point to another directories (or even files) within the same or another svn-repository.
Assuming I have a repo-structure like this:
root |-> dir1 | |-> file1.1 | \-> file1.2 |-> dir2 | |-> file2.1 | \-> file2.2 |-> dir3 | |-> file3.1 | \-> file3.2 |-> svn-external to: root\dir1 \-> svn-external to: root\dir2\file1.1
If I call
svn checkout svn://root/dir3/ workspace
the local directory "workspace" will look like the following:
workspace |-> file3.1 |-> file3.2 |-> file2.1 \-> dir1 |-> file1.1 \-> file1.2
As you can see subversion automatically followed the svn-external links and checked out directory "dir1" as subdirectory and "dir2/file2.1" as file.
That is why I think it would be a very useful feature for Redmine, to not only show the svn-externals as property values, but also to evaluate them and display the appropriate source together with its log-messages. (Eventually, one could make it an optional behavior that could be switched on or off, for backward-compatibility.)
Of course, with #779 implemented in Redmine 1.4.0 I could just add an extra repository for each svn external by hand, but that can be much work if one uses svn externals a lot. (And still, I would be unable to see all changes at a glance, without clicking through all repositories.)