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 projects are in single repo
The reason I mention it is that when you commit, the revision number of the *repository* increases. There is no such thing as the revision number of a *project*, unless coincidentally you keep each project in its own repository. (Subversion doesn't even know what a project is. It just knows about repositories, which contain files and directories.) If you had a separate repository for each project, and a separate repository for your shared modules, then there would be truth to the statement that committing a change to the module wouldn't increase the revision of the other projects' repositories. But if everything's in one repository, then committing anywhere in that repository increases the revision of the repository. > but I wonder about making them > separately (are there any advantages of it?) There are advantages and disadvantages. There's a wealth of information in the mailing list archives on this topic. Use whichever way works for you.
