[
https://issues.apache.org/jira/browse/JENA-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940803#comment-16940803
]
Claude Warren commented on JENA-1704:
-------------------------------------
My reading of
https://docs.sonarqube.org/latest/architecture/architecture-integration/ is
that we would have to run SonarScanner as part of the build process for the
sonar service ( SonarQube Server and SonarQube Database) to report it.
We could do this as part of the site processing and just add site processing to
the nightly build. I think this would give us the speed we like for
development, a nightly or on-demand report of the state of the code base as
well as SonarQube reports.
I could be wrong about all of the above.
> 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: Adam Soroka
> Assignee: Adam 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
(v8.3.4#803005)
