Java Maven – How to Include Module Source Files into War File

Since you already have your projects ready for Maven and Jenkins is installed, you may go one step further and install Sonar. It is an incredible code quality related tool, it performs Cobertura, Checkstyle, FindBug, and many other analysis tools at the same time. That way, the code quality reporting is done by Sonar, not by Maven or Jenkins.

You can install Sonar on the same machine where Jenkins is installed or somewhere else. If you just want to test it, you can just perform the standard install (it uses its own HSQLDB if you don't configure the database yourself) and you are almost ready to go. The last thing you need is to configure the relationship between Jenkins and Sonar.

There is done via the Sonar plugin for Jenkins. Once you have installed the plugin:

1. Indicate where Sonar can be located on the Jenkins configuration
2. For each build job you want to be analysed, go into the job configuration and check the "Sonar" checkbox.

Be careful for one thing: the analysis may be quite long for big projects. But then again, you may configure special nightly Sonar builds in addition to standard builds.

Hope that helped.

Given a directory structure of

/foo/A/pom.xml
/foo/B/pom.xml
/foo/C/pom.xml

you need to introduce

/foo/pom.xml

and that should specify A, B and C as modules. You can now do cd /foo; mvn clean install and have A, B, and C recompiled. If your dependencies are correct, they even do so in the correct order.