[
https://issues.apache.org/jira/browse/JENA-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830142#comment-16830142
]
Andy Seaborne commented on JENA-1704:
-------------------------------------
I originally thought the reports are generated separately from the build - then
it works for anyone using the build whether they have access to send results to
Apache or not. This makes sense because there is a magic key for the reports in
SonarCloud. But the mentions of POM changes suggests otherwise.
Give it a go and we can see what happens.
> 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)
