> 1. Yes you're right, but even though I've done committing and updating
> externals I got the same message "svn: 'BigProject-trunks\Project1' is not
> under version control".
>
> 2. The usual way to create a tag doesn't fit our need of tagging all
> projects within one revision.
>
> For better understanding:
> - BigProject consists of 9 Projects
> - Each of projects has branches, tags and trunk
> - Branches are created from projects' tags
> - Projects are maintained by different groups of developers
> - Each of developers doesn't have access to all projects
> - Release of BigProject is performed by one senior developer
> So how can I tag all trunks of projects within one revision instead of
> using bunch of "svn copy url1 url2"?:
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
