Guten Tag Marc Davenne, am Mittwoch, 26. Juni 2013 um 16:36 schrieben Sie: > Files who should not be on SVN : > > files automatically generated
This depends on the files which get automatically generated and their purpose: It's perfectly valid to version automatically generated class stubs e.g. for web service clients and servers which get manually changed afterwards or simply to make sure that one generated version stays exactly the same and doesn't use new interface names, automatically generated GUID or whatever those tools out there implemented. > files containing specific information about my > development environment (so properties files for example) Depends again, it's perfectly valid to version project files of Eclipse, Visual Studio or whatever you use to assure that every member of you project use the same settings etc. > executable files Depends again?! ;-) There a some projects out there which version executables, MSI packages and stuff like that and provide direct download access to their customers using some web application like ViewVC or WebSVN. If you have an environment were your executables are not build automatically using some kind of CI, Hudson, Jenkins, whatever, versioning manually build and once tested applications can save a lot of time. Besides that, one may be in an situation were one has only access to third party, pre compiled libraries in which case there may be no reason to not version those, too. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
