On Apr 19, 2010, at 04:36, ja...@smars.pl wrote:
>>> when I commit changes on either trunk, this change is made only on
>>> /share/module_1234 (the revision number of project1 or project2 will not
>>> increase).
>>
>> I guess you have each project in its own repository? Ok.
>
> Actually all pro
>
> On Apr 19, 2010, at 03:53, ja...@smars.pl wrote:
>
>> Ok, it seems to be ok but has some disadvantages:
>>
>> when I commit changes on either trunk, this change is made only on
>> /share/module_1234 (the revision number of project1 or project2 will not
>> increase).
>> Because of the above th
On Apr 19, 2010, at 03:53, ja...@smars.pl wrote:
> Ok, it seems to be ok but has some disadvantages:
>
> when I commit changes on either trunk, this change is made only on
> /share/module_1234 (the revision number of project1 or project2 will not
> increase).
> Because of the above there is no i
Ok, it seems to be ok but has some disadvantages:
when I commit changes on either trunk, this change is made only on
/share/module_1234 (the revision number of project1 or project2 will not
increase).
Because of the above there is no information in show log of
project1/project2.
The trunk history
The SVN solution for this use case svn:externals ([1]).
Basically, you would have a single instance of module_1234:
/share/module_1234
and in each project you use that module,
you define the svn:externals property to point to that module:
/project1/trunk - svn:externals = ^/share/module_1234 module
have you looked into svn:externals
On 19 April 2010 08:41, wrote:
> hello
>
> I have a situation, where there are two(or more) projects with its trunks,
> and some modules in these trunks are the same:
>
> /project1
> /project1/trunk
> /project1/trunk/module_123
> /project1/trunk/module_1234
> /
