Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.0.3
-
Fix Version/s: 3.0.4
-
Component/s: None
-
Labels:None
-
Environment:Maven 3.0.3
-
Complexity:Intermediate
-
Number of attachments :
Description
As described in SONAR-2626 : aggregator mojo, which requires dependency resolution (like "sonar:sonar" or "javadoc:aggregate-jar") is unable to resolve dependencies, when executed from command-line and build extension with custom packaging declared in sub-module, but not in parent. Declaration of extension in parent allows to workaround problem as well as downgrade to Maven 2.2.1 and execution of "mvn validate sonar:sonar".
Issue Links
- is depended upon by
-
SONAR-2626
Sonar Maven plugin tries to resolve the wrong files on custom packaging type
-
- is related to
-
SONARPLUGINS-991
Unable to execute Sonar with Maven 3.x for all projects in forge
-
Fixed in r1151424.