Jeffrey Kesselman wrote:
> Id be interested to know what "best practoice" is violated by giving
> each projectits own repository. In our case, where each project is
> unique and has a unique list of qualified users, it seemd not only the
> simpelst but also the most obvious way to organize our SVN server.
There's nothing wrong with each project being in its own repository, as
long as they are truly independent. Subversion best practices call for
the root directory of a repository to contain only the "trunk",
"branches", and "tags" directories. The actual project code would be
contained within the "trunk" directory, which is then copied to a subdir
of "branches" or "tags" to branch or tag the code. This is discussed in
detail in the svn book: http://svnbook.red-bean.com/
So if you follow that best practice, your .project file would be within
the trunk directory, not in the root, and Subclipse would be able to
check it out from there.
Received on Mon Aug 8 22:18:40 2005