[ 
https://issues.apache.org/jira/browse/SLING-9414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099055#comment-17099055
 ] 

Bertrand Delacretaz commented on SLING-9414:
--------------------------------------------

Thank you for this! The build was fixed indeed but I think we can disable 
SonarQube for the website build, I did that in 
https://github.com/apache/sling-site/commit/1a648d8c12ab3403b64731358bb99eb5e75dd1fd

> Allow to disable SonarQube run via module descriptor
> ----------------------------------------------------
>
>                 Key: SLING-9414
>                 URL: https://issues.apache.org/jira/browse/SLING-9414
>             Project: Sling
>          Issue Type: Improvement
>          Components: Tooling
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In the context of 
> https://lists.apache.org/thread.html/ree9107867e5023e5bf468ffd34161d5226ed14dc01ba8dad3dffb8e5%40%3Cdev.sling.apache.org%3E
>  it became obvious that in some cases SonarQube execution are not useful and 
> should be disabled.
> In addition it would make sense to optionally not use the 
> {{additionalMavenParams}} 
> (https://cwiki.apache.org/confluence/display/SLING/Sling+module+descriptor) 
> for the SonarQube run in 
> https://github.com/apache/sling-tooling-jenkins/blob/96d11259bb003d4ff07a089d0fb66a48f8123ddb/vars/slingOsgiBundleBuild.groovy#L39.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to