[
https://issues.apache.org/jira/browse/JENA-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825193#comment-16825193
]
A. Soroka commented on JENA-1704:
---------------------------------
I'm not sure we're talking about the same thing, here, [~andy.seaborne]. I'm
talking about adding a build step to send the data to Sonar (at Apache) and
that's it. I'm not talking about failing builds or giving anyone any feedback
at all. If anyone is interested in Sonar's opinions, they would have to
actually go to [https://builds.apache.org/analysis] themselves and look for it.
Does that seem less problematic? The interest of [~acoburn]'s advice is that if
a module has problems running Sonar we don't have to fix them to use it for
other modules.
> 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)
