Which one is the best structure for Android SVN?

What is the best SVN repository structure that will contain one Android project (and why)?

http://myserver/svn /trunk /MyProject /src /res /assets /branches /tags 

or

 http://myserver/svn /trunk /src /res /assets /branches /tags 

Basically, I want to know whether to explicitly specify the project root folder in the hierarchy. The repository will contain only one project, but it will have many branches and tags. I am using Eclipse with the SVN plugin.

Thanks,

Barry

+7
source share
2 answers

I would like it:

 http://myserver/svn MyProject1 /trunk /src /res (external) /assets /branches /tags MyProject2 /trunk /src /res (external) /assets /branches /tags resources 

Did not do much of Android development, but things like resources that I usually keep outside the main source structure and use svn:externals to connect thoughts and potentially use them in different projects

+1
source

What I usually do (for both Android and other technologies like PHP, as well as for SVN and other version control software like Bazaar or Git), looks something like this:

 http://myserver/svn /MyProject /trunk /sources /src /res /assets /ressources => Here, I can put text files, documentation, ... that is really part of the projet -- but not part of the application /branches /tags 


So very close to your first idea, except:

  • I can have several projects on my SVN server,
  • Each project has its own connecting lines / branches / tags
  • In each project, I have the source code; and some other directories that are not part of the application, but related to it enough to be in the SVN project.
+5
source

All Articles