Developers should prepare their workspace by configuring code style and formatter preferences and including at least two source folders. The code should be formatted and cleaned regularly using provided commands. Developers must follow coding standards like using packages and one class per file. Unit tests are required by having a test class for every code class. Code should be checked in regularly without waiting for coding to finish. Useful commands are provided to create JAR files and generate Javadoc.

2. Development Rules
• *Prepare* your workspace/project
– Window -> Preferences -> Java -> Code Style
• Clean up
• Formatter
• Code templates
– At least two source folders in Java project
• src/main/java
• src/test/java
– Output folder
• target

3. Development Rules (contd.)
• Format/Clean up the code regularly
– Right click -> Source -> Clean up
• Entire project or just one file
– Ctrl + Shift + F (format code)
• PMD/ Style Check regularly
– Right Click -> PMD -> Check code with PMD
– Right Click -> Check Style -> Check code with
Check Style

4. Development Rules (contd.)
• Java coding
– Always use packages
– One class / file
– Never use System.out.print* methods
• Junit
– Test class for every class
• Check-in regularly
– Don’t wait for coding to get over

5. Useful commands
• To make jar files
– jar cvf <jar file>.jar –C target/
com/evolvus/training/anisht/<*.class>
– jar cvf <jar file>.jar –C target/ .
• To generate javadoc for package
– javadoc –d html –sourcepath srcmainjava
com.evolus.training.anisht

6. Questions?

7. Thank You.