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

A. Soroka commented on JENA-1704:
---------------------------------

On 
[dev@jena|https://lists.apache.org/thread.html/3d41d82bbe5307346059e0cb03723e3e6da3d1681b412341ac881a2a@%3Cdev.jena.apache.org%3E]
  [~acoburn] remarked:

 
{quote}{color:#000000}It is possible to exclude specific modules from Sonar's 
analysis (I do this{color}
{color:#000000}with some of my own projects). The documentation for this is 
here:{color}
[https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner+for+Maven#AnalyzingwithSonarQubeScannerforMaven-ExcludingamodulefromSonarQubeanalysis]

{color:#000000}Basically, you define this property in the module you want to 
skip:{color}
{color:#000000}<sonar.skip>true</sonar.skip>{color}

{color:#000000}Aaron{color}
{quote}

> Enable Apache Sonar reports
> ---------------------------
>
>                 Key: JENA-1704
>                 URL: https://issues.apache.org/jira/browse/JENA-1704
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Build
>            Reporter: A. Soroka
>            Assignee: A. Soroka
>            Priority: Trivial
>
> Apache offers a Sonar service at [https://builds.apache.org/analysis.] We 
> should take advantage of it in a non-intrusive way. Enabling Sonar analysis 
> must not annoy anyone working on the codebase or make development less 
> pleasant, so it must be done carefully.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to