Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: ANT-TASK-2.0
-
Component/s: Ant Task
-
Labels:None
-
Number of attachments :
Description
The purpose is to deprecate the way "sonar.modules" work.
Old mechanism:
- "sonar.modules" is a list of paths that point to Ant scripts.
- Those scripts are loaded to define the module definitions
- This causes some issues (see
SONARPLUGINS-2156) plus the fact that it is not flexible not reusable in tools like Gradle
New mechanism:
- It will rely on the multi-module support implemented for the Sonar Runner (see
SONARPLUGINS-2202) - It will be possible to specify the multi-module structure using either:
- only properties in the root project (like explained in
SONARPLUGINS-2202) - a mix of properties of the root project and "properties" files located in modules
- only properties in the root project (like explained in
Notes:
- the "old" mechanism will still be available as "compatibility mode"
Issue Links
- depends upon
-
SONARPLUGINS-2202
Add multi-module support
-
- is depended upon by
-
SONARPLUGINS-1454
Sonar Projects using Ant task do not have submodule hierarchy in dashboard
-
I'm a little confused by the description of the new mechanism. Since the multi-module structure will now refer to property files rather than Ant scripts, does this mean that the Ant Task will now require the Sonar Runner in order to perform multi-module analysis?