RE: Subproject organization question

-----Original Message-----
From: Tad Marko [mailto:tad.markobhnetwork.com] 
Sent: Thursday, November 01, 2007 6:55 PM
To: userssubversion.tigris.org
Subject: Subproject organization question

> Projects here contain multiple subprojects, so one has
to dig about
inside 
> of the trunk, branches or tags directories looking for
the actual
project 
> you want to check out since we have these conventional
directories at
the 
> top of each project.


If they're doing:
	trunk/project1
	trunk/project2
	trunk/project3
	branches/project1/branch1
	branches/project1/branch2
	branches/project2/branch1
	branches/project3/branch1

then yes, that's a pretty gawd awful way of organizing
things.  


>	project-->sp1-->trunk-->[eclipse project files
and code dirs
with code]
>	       |     |->branches-->[copies of trunk]
>		 |     -->tags-->[copies of trunk]
>             |
>             |--sp2-->trunk
>                   |->branches
>                   |->tags


I'm not an Eclipse jockey, but from what little I've done
with it, there
shouldn't be a problem.

Subversion doesn't care how you organize your repository. 
Humans who
have to find projects, do merges, write hooks, automate
builds, write
scripts, etc. do care, so you might want to talk it up
first, before
pulling the rug out from under people.

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribesubversion.tigris.org
For additional commands, e-mail: users-helpsubversion.tigris.org