 |
History
| Log In
|
|
|
|
This structure should be optional. Not all repositories will follow Ciao, – This structure should be optional. Not all repositories will follow Ciao, – This structure should be optional. Not all repositories will follow Ciao, – This structure should be optional. Not all repositories will follow Ciao, – This structure should be optional. Not all repositories will follow Ciao, – This structure should be optional. Not all repositories will follow Ciao, – This structure should be optional. Not all repositories will follow Ciao, – This structure should be optional. Not all repositories will follow Ciao, – This structure should be optional. Not all repositories will follow Ciao, – This structure should be optional. Not all repositories will follow Ciao, – This structure should be optional. Not all repositories will follow Ciao, – |
|||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Normal
Import into VCS when creating a new project
Once imported, the trunk version of the repository should be checked out into the chosen local filesystem directory. This (suggested) repository layout is outlined in Chapter 4, Section 2 of the Subversion book ( http://svnbook.red-bean.com/en/1.0/ch04s02.html
).
NOTE: The branches and tags locations on the server-side should be used for tagging/branching code elsewhere in Subverion VCS code.
CVS, Perforce, and other supported version control systems should do the same thing, creating default server side layouts as is expected by those systems.
Example:
User creates project "footest" in c:\projects for the the repository:
svn+ssh://mark@myserver:/data/svn/projects/footest.
IDEA should create:
/data/svn/projects/footest/trunk
/data/svn/projects/footest/branches
/data/svn/projects/footest/tags
And checkout svn+ssh://mark@myserver:/data/svn/projects/footest/trunk to c:\projects\footest
AFTER this step IDEA would create the relevant directories for src/test etc. etc.
This will allow the user to commit to the project straight off the bat.