Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: SONAR-RUNNER-2.0
-
Component/s: SonarQube Runner
-
Labels:None
-
Number of attachments :
Description
This feature will be based on properties to define the multi-module structure.
It should be possible to declare the following in the "sonar-project.properties" file:
... sonar.modules=mod1,mod2,mod3,mod4 # a module has to redefine at least "sonar.projectName", as its key and its base directory has inferred from its identifier ('mod1' in this case) mod1.sonar.projectName=Module 1 # but a module can obviously override properties mod2.sonar.projectKey=org.company.mod2 mod2.sonar.projectName=Module 2 mod2.sonar.sources=java-sources # also, a module is not necessary located in a direct sub-folder mod3.sonar.projectBaseDir=modules/mod3 mod3.sonar.projectName=Module 3 ...
It should be highlighted that the key of a module is automatically prefixed by the key of its parent followed by a semi-colon, in order to:
- prevent duplicate key problems in Sonar
- make it possible to analyse a module outside of its parent
Issue Links
- is depended upon by
-
SONARPLUGINS-2224
Improve multi-module support
-
For your tests Freddy, you can use the draft documentation located here: http://docs.codehaus.org/display/SONAR/Multi-module+support+for+Sonar+Runner