Describes recommended uses for some tools.
It basically is a reminder how to use a tool so as not to fall into traps.



Subversion comes with native CLT client. But there are plenty of graphical ones and integrations into IDEs.
Because of of refactoring issues the recommendation is:

  • OSX: versions + integrations (IDEA)
  • windows: tortoise + integrations
  • linux: ? + integrations

Directory layout

Use the subversion standard, i.e. development in trunk, branches in branches.


  • update often
  • checkin complete changes


  • use the IDE for refactoring but don't move or rename folders or packages.
  • for folder operations only in the repository directly and than update all clients. This seams to be a svn bug so all clients break equally.


svn can be configured, but the config files lives on the client only. Server side configuration must be done through the local
config file and must be done on all clients.


in config:
global-ignores = *.iml *.iws *.ipr build target

These can be set in cone client.


enable-auto-props = yes
*.txt = svn:mime-type=text/plain
*.html = svn:mime-type=text/html
*.css = svn:mime-type=text/css
*.png = svn:mime-type=image/png
*.jpg = svn:mime-type=image/jpeg

These must be set on all machines so that import behaves correctly

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License