CridManager 2.0 - Team settings

To make a team development easy, it's a good idea to have most of the team settings identical for all team members.

This is, of course, not a must, but if you in any way can use the settings described here, please do.

All team settings that can be exported in any way, can be found in the SVN at project-settings.

IDE

The IDE used by most of the team members is Eclipse. If you haven't ever heard of Eclipse as a java programmer, you really missed something out on.

Intelli-J IDEA seems to be adequate or even better, but it costs.

To get started with Eclipse and set up all projects currently in the repository, read CridManager 2.0 - Getting started.

Code formatting

When working with several coders in a repository, code formatting becomes an important issue to make changes trackable. If we're working with different code formatting settings, any committ will create a huge amount of changes which are formattings only. Therefore, you have to import and use the file CodeFormat.xml, containing the code formatting option for Eclipse. Import with

• menu Window -> Preferences
• setting Java -> Code Style -> Formatter
• Import... and select the file

Code templates

Please use the following code templates. They gurantee that all class files have identical headers. there's not much else in there beyond that. Load and import the file codetemplates.xml. Use

• menu Window -> Preferences
• setting Java -> Code Style -> Code templates
• Import... and select the file

Ant scripts

No project of a decent size can do without build automation. We use Ant, because of it's tight integration into Eclipse. To use some special features, the following additional plugins need to be installed:

Ant4Eclipse

Ant-Contrib

They are in the lib project as well, so updating this project is adequate. Add them to the ant runtime classpath

• "Window->Preferences - Ant->Runtime"
• Tab "Classpath", Setting "Global Entries" add the libs ant4eclipse.jar, ecj.jar and ant-contrib.jar

Automatic Builds

To have alle changed projects being compiled and the jars copied to the core project, do the following (on the example of the de.cridmanager.filesystems project):

• Open project settings of de.cridmanager.filesystems
• select Builders
• New -> Ant Build -> OK
• enter any senseful name
• Tab "Main" select build.xml, Base Directory is the project dir
• Tab "Targets": Target "copyJarToCore" as Target for "Auto Build"
• OK -> OK

Downside: ant is started after ANY save inside the project. If it does not suite you, don't do it.

Unit testing

Unit testing is a must. Use Eclipse's excellent integration of jUnit 3.8 (this is what we currently use - can be discussed to upgrade to jUnit 4). Read more at the Unit testing page.