Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current ·  View Page History
<< Previous Version 78 Next >>

Best practices

  • Build with maven before committing into SCM (Git or Subversion)
  • Commit frequently
  • Do not commit incomplete changes (SCM is not a backup system)
  • Do not commit IDE files (.settings, .project, .classpath, .idea, *.iml, *.ipr, *.iws)
  • Use meaningful comments when doing a commit, always with the JIRA key and title (e.g. "SONAR-6 Apply license LGPL") - see Note About Git Commit Messages
  • Subscribe to the mailing list dev@sonar.codehaus.org
  • Overuse JUnit tests with the help of FEST Assert and Mockito
  • Think IoC (Inversion of Control pattern)
  • Don't reinvent the wheel : use standard libraries like commons-lang, commons-io and guava (formerly known as google-collections). Commons-collections is deprecated since Sonar 1.10.
  • Use comments and javadocs only when necessary
  • API Javadoc - use "@since <version>" and "@deprecated in <version>"
  • Do not forget the license header on all the Java and Ruby files
  • Respect the code formatting described below
  • Follow error handling guidelines
  • Eat your own food : have a look at Sonar and Sonar plugins on Nemo.
  • Follow Maven conventions

Source Encoding

Source code encoding should be set to UTF-8 to prevent cross-platform encoding issues.

UTF-8 is specified in parent POMs, so it is used by Maven when building the projects. However, it may not be set by default in your prefered IDE. The best practice is to force it for all your source code.

  • For Eclipse : go to "Preferences -> General -> Workspace" and force the "Text file encoding" to "UTF-8"
  • For IntelliJ IDEA : go to "Settings -> File Encodings" and force the "IDE Encoding" to "UTF-8"

Code Style

  • Classes with acronyms are CamelCase : for example prefer PmdPlugin to PMDPlugin, or JavaNcssHandler to JavaNCSSHandler

  • Configure your IDE with the correct code style: see the section "IDE Support". 

Edit Ruby code

The development mode is used to edit Ruby on Rails code. The application is automatically reloaded when Ruby files are saved. It avoids restarting the server. Changes are reloaded on the fly. Execute one of the following commands from the sonar-server/ directory to start the server :

Then ruby code can be directly edited from sonar-server/src/main/webapp/WEB-INF/app.

Debug Maven Analysis

  • Execute mvnDebug instead of mvn :

  • Attach your IDE to the remote process (the listening port is 8000).

Example in Intellij Idea : Run -> Edit configurations -> Add new configuration -> Remote -> port 8000.

Profile Maven analysis with JProfiler

  • Clone $MAVEN_HOME/bin/mvnDebug to mvnJProfiler and replace the MAVEN_DEBUG_OPTS property by :
    MAVEN_DEBUG_OPTS="-Xint -agentlib:jprofilerti=port=8849 -Xbootclasspath/a:/Applications/jprofiler5/bin/agent.jar"
  • Start JProfiler -> Connect to an application on a remote computer

Tips and tricks

Connect to Derby from command line

  • download derby (the same version as used by sonar)
  • set the DERBY_HOME property
  • execute the command $DERBY_HOME/bin/ij

  • connect to the database :

Compare XML files in JUnit

Use XMLUnit. The dependency is already defined into maven.

Warning : There's a bug on the similar() method. Contrary to the documentation, it fails if nodes are not in the same order.

Freeze Ruby gems

Ruby gems are used in the webapp (directory src/main/webapp of the sonar-server module). They are delivered with the application. To install or upgrade a gem :

  • copy the gem from local ruby installation into WEB-INF/vendor/gems.
  • execute "jruby -S gem specification <gemname> > .specification" from WEB-INF/vendor/gems/<gemname>. It generates the .specification file.
  • commit the directory WEB-INF/vendor/gems
Labels
  • None