Thanks for simple option 1, it could solve our problem.
Option 2 doesn't fit, cause of needing to do bunch of "svn copy ..." to tag
all projects and then tag to BigProject with pinned externals.
Of course it could be done without tagging all projects, just pinning
externals to revision of trunk, but it is too complicated to automate.
And last question, is it a bug when I got the message "svn:
'BigProject-trunks\Project1' is not under version control", when I want to
svn copy multiple svn:externals paths to url?
On Mon, Jun 14, 2010 at 7:14 PM, Bob Archer <Bob.Archer_at_amsi.com> wrote:
> Option 1:
>
> Created a nested project folder layout:
>
> /Bigproject9/trunk
> SubProject1/trunk
> /branches
> /tags
> Subproject2/trunk
> /branches
> /tags
> /branches
> /tags
>
> Option 2:
>
> Create a folder in the root of the repo BigProject9Tags that is nothing
> more than a folder for each release with pinned externals to the versions of
> each sub project tags that are included in the bigproject release version.
>
> BOb
>
Received on 2010-06-18 10:25:25 CEST