SVNSince SVN is prone to get messy when not controlled correctly, I'm setting up some guidelines.
- If you want to commit a new project or package, ask me (from now on I will act as SVN admin). I will tell you where you can put it.
- Every developer will get his own directory in the repository, where he is free to do what he wants.
- For the official projects (Victory Engine, RPG game, etc.) maintain the trunk/tags/branches layout
- Don't commit generated files (.class files, javadoc pages, test reports, ...) and location-specific files (.project, build.properties, ...)
- For non-trivial commits (moving a file, creating a new directory, things that don't affect the content of files) include a descriptive comment
-
Update before starting editingCode conventionsTo better allow multiple developers to work on the same code, a coding convention must be followed. This convention has been made in the form of a
Checkstyle configuration file, which can be found on SVN at
artifacts/conventions/sourcecode/checkstyle.xml. You can import this file into
Eclipse-CS, an eclipse plugin which uses checkstyle to automatically check your code while you are developing.
In the same directory on SVN you will find
eclipseformatter.xml and
eclipsecleanup.xml. In the eclipse preferences you can import these files as Java formatter and cleanup respectively, after which you can use "Source->Clean Up" in your editor to automatically change your code to follow many of the conventions.
You will also see a file snippet.xml, which you can import in eclipse. Snippets are handy pieces of code (currently they include subheaders for seperating constructors, methods, fields and getters/setters) which you can drag into your code from the Snippets view in Eclipse.
Development Guidelines
