Best practices for good development patterns, i.e. all the (small) things that programmers regularly do and how it is done well, are collected at BestPractices.
A common code format style is advantageous for collaborative development, becauser reformatting does not cause SCM systems to discover changes where there weren't any but just some reformatting. So please use the Eclipse Code Formatter as described here
BestPracticeJarsInMaven - How to include libraries, i.e. jar files or dll's, into Maven projects which are not available in on-line repositories, for example because of licensing issues, patched versions, or custom libs.
BestPracticeDifferentPropertySetsInMaven - How to separate different property sets containing sensible property information for arbitrary target environments (test, development, serverA, serverB, etc)
If your jobs fails because of the wrong javac version, take a look at the configuration and try to select the correct one via JDK dropdown. If your required version is not available, go to global configuration and add a new JDK with the required version and select an installer.
Put an angel on your shoulders while programming: create and run JUnit Tests.
Source Code Management
GitFAQ is the entry point to all GitHub documentation