You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Kevin Risden (JIRA)" <ji...@apache.org> on 2018/09/19 20:15:00 UTC
[jira] [Commented] (CALCITE-338) Investigate if integration with
SonarQube is worth doing
[ https://issues.apache.org/jira/browse/CALCITE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621144#comment-16621144 ]
Kevin Risden commented on CALCITE-338:
--------------------------------------
For reference the Apache Sonarqube instance moved to https://builds.apache.org/analysis
> Investigate if integration with SonarQube is worth doing
> --------------------------------------------------------
>
> Key: CALCITE-338
> URL: https://issues.apache.org/jira/browse/CALCITE-338
> Project: Calcite
> Issue Type: Task
> Reporter: Vladimir Sitnikov
> Assignee: Julian Hyde
> Priority: Major
>
> SonarQube (http://www.sonarqube.org/) collects metrics from the source code, plots trends, etc.
> They used to integrate checkstyle, findbugs, pmd, and similar tools, however the latest trend in SQ is to implement SQ-specific checks, so they aim to have a solid set of checks.
> Here are some live instances:
> http://nemo.sonarqube.org/
> http://analysis.apache.org/
> Motivation:
> * SQ might be better alternative to checkstyle
> * better visualization for non-blocker issues. For instance, low/minor problems like "too big class file" will be more visible
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)