Build system

Clover sources are organised into individually build-able modules.

Module layout

Each module lives in a separate top-level directory with its own build file. The rough template is:

/
+--<module-name>
|  +--src
|  |  +-- main
|  |      +--java|groovy - source for the module
|  |      +--resources   - miscellaneous resources like icons
|  +--src
|  |  +--test
|  |     +--groovy       - test sources (unit testing, based on Groovy JUnit)
|  |     +--resources    - extra tests (integration tests, based on different frameworks)
|  +-- pom.xml           - local build file for a module
|
+--pom.xml               - root pom.xml

Day-to-day development

• If you are working on a particular module, you can either call build targets on the local module build file or from the global build file.
• All output from a module build is put under /<module-name>/target
• Before checking in, you should run at least mvn test for clover-core, clover-ant and clover-groovy modules.