Quoting Jing Xue <mailto:jxue01@digizenstudio.com>:
> Quoting Sonnenmoser Kurt <Kurt.Sonnenmoser@aris-geoservices.ch>:
>
>> Any hint about how others have solved (or not solved) this problem,
or
>> whether others would also like to see the mentioned enhancement,
would
>> be very much appreciated.
>
> Wouldn't it be better to deal with code dependencies in the realm of
> the build tool rather than that of the CM?
For a solution in which the build tool, VS.NET in our case, is
involved more intensely, we have made the following considerations:
The goal is to check out all relevant code with a single command
and to keep references to common code with the projects, not with
the solution, which is what I am trying to achieve with the
suggested SVN enhancement described in my original posting
http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=69033.
Currently we attach externals definitions to the solution directory,
involving some book-keeping of redundant information in all solutions
containing a certain project when the latter newly references an
additional project.
In our opinion, it would be desirable to store the repository URL
(and the revision) with the project references. The IDE should collect
these URLs and check out the corresponding code. If two projects
reference the same common third project, the latter should be checked
out only once.
Does anyone know whether there is a VisualStudio-Plugin that features
this kind of functionality?
Again, thanks for any hint.
Kurt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 16 13:44:14 2007