An SCM is IMHO not the best place to store the binary files produced by a
build - I prefer only storing the sources and building a specific version on
demand. I do understand that it can make sense to have fast access to
complete builds but I would recommend storing these builds in a separate
repository (this would also make it easier to manager permissions to
"binary-only" releases when required).
So you could have for example:
{svn_src_repo_1}/.... (as below without the "deployment")
And
{snv_dist_repo_1}/trunk/ (that is your current release)
{snv_dist_repo_1}/tags/ (here are your previous releases)
-----Original Message-----
From: Subversion List [mailto:subversion@emalbum.com]
Sent: Wednesday, December 01, 2004 4:12 PM
To: 'Lewis Gardner (TYCO)'; users@subversion.tigris.org
Subject: RE: Repository layout
Thanks Lewis.
What do you think of this structure:
{svn_repo_1}/branches
{svn_repo_1}/tags
{svn_repo_1}/trunk/JavaProject1
{svn_repo_1}/trunk/JavaProject1/src
{svn_repo_1}/trunk/JavaProject1/docs
{svn_repo_1}/trunk/JavaProject2
{svn_repo_1}/trunk/JavaProject2/src
{svn_repo_1}/trunk/JavaProject2/docs
{svn_repo_1}/trunk/JavaProject3
{svn_repo_1}/trunk/JavaProject3/src
{svn_repo_1}/trunk/JavaProject3/docs
{svn_repo_1}/trunk/JavaProject4
{svn_repo_1}/trunk/JavaProject4/src
{svn_repo_1}/trunk/JavaProject4/docs
{svn_repo_1}/deployment
{svn_repo_1}/deployment/current
{svn_repo_1}/deployment/archive
{svn_repo_1}/dependencies
{svn_repo_1}/dependencies/CommonNet
{svn_repo_1}/dependencies/CommonNet/current
{svn_repo_1}/dependencies/CommonNet/archive
{svn_repo_1}/dependencies/ORO
{svn_repo_1}/dependencies/ORO/current
{svn_repo_1}/dependencies/ORO/archive
{svn_repo_1}/dependencies/Log4J
{svn_repo_1}/dependencies/Log4J/current
{svn_repo_1}/dependencies/Log4J/archive
The dependencies are all 3rd party/vendor libraries. The deployment
directory will contain the jar files from the 4 projects.
-----Original Message-----
From: Lewis Gardner (TYCO) [mailto:lgardner@tycoint.com]
Sent: Tuesday, November 30, 2004 8:44 PM
To: users@subversion.tigris.org
Subject: RE: Repository layout
If all four projects are small or medium sized then you can load them all
into one repository, for example:
{svn_repo_1}/branches/
{svn_repo_1}/tags/
{svn_repo_1}/trunk/JavaProject1
{svn_repo_1}/trunk/JavaProject2
{svn_repo_1}/trunk/JavaProject3
{svn_repo_1}/trunk/JavaProject4
The advantage of having all 4 projects in the same trunk is that you can
easily update/commit all four projects at once. The disadvantage is that
tagging and branching can become more complicated --- if you plan on doing
lots of branches then you are better off creating the branches/tags/trunk
directories per project.
The dependency of projects 1 to 3 on project 4 can be easily resolved by
a) using Ant: refer to the jar file in JavaProject4 via relative path
(../JavaProject4/dist/project4.jar)
b) using Eclipse: list JavaProject4 under "Project References" in projects 1
to 3
________________________________________
From: Subversion List [mailto:subversion@emalbum.com]
Sent: Wednesday, December 01, 2004 3:22 PM
To: users@subversion.tigris.org
Subject: Repository layout
I have 4 java projects that I am working on and needs some advice on how to
"best" setup the repository/repositories.
JavaProject1, JavaProject2, and JavaProject3 all have a dependency on
JavaProject4. In each project, there will be a src, docs, and classes folder
along with a variety of configuration files. Each project ends up as a jar
file so I also want to keep track of those.
I am not sure rather I should create 4 repositories or just 1. Any
suggestions on how to set this up? I'm not quite sure how to deal with the
jar files and the fact that projects 1-3 depend on the jar file from
project4.
Thanks in advance.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 1 06:28:55 2004