[
https://issues.apache.org/jira/browse/JENA-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825227#comment-16825227
]
Andy Seaborne commented on JENA-1704:
-------------------------------------
The details of what is being proposed are unclear to me.
What does it take to enable Sonar analysis?
Surely [https://builds.apache.org/analysis] does not need any POM changes (no
plugin, that's for a local report?) because a key is involved. I assumed that
it was an externally run report on a regular cycle, not triggered every build.
Is that not the case? How do other people build jena on their systems?
If it is in-maven-build, then it slows the build down. So I'm against a sonar
report for -Pdev which i use all the time locally, and prefer that it was not
part of the regular builds but a separate Jenkins job.
> 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)
