[jbosstools-issues] [JBoss JIRA] (JBIDE-22439) Tests: include different checkers in our build or jenkins

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243072#comment-13243072 ] 

Mickael Istria commented on JBIDE-22439:
----------------------------------------

And by the way, I'm -1 for adding this in Jenkins. Indeed, contributors must be able to see the failure locally if they cause it, putting logic in Jenkins makes that contributors won't even be aware of the quality constraints when contributing.
Also, you could consider enabling FindBugs nature in your .project and committing the .settings; so people who have FindBugs plugin installed would get the feedback from FindBugs in their IDE directly, so they can work on it as they're coding.

> Tests: include different checkers in our build or jenkins
> ---------------------------------------------------------
>
>                 Key: JBIDE-22439
>                 URL: https://issues.jboss.org/browse/JBIDE-22439
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: openshift
>    Affects Versions: 4.4.0.Alpha2
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>             Fix For: 4.4.0.Alpha3
>
>
> We should have different checkers in our build so that problems are forced on us. Just having them in sonar isnt good enough since it tends to get forgotten.
> - PMC
> - Code-format-Checkers
> - Code-duplication (like [cpd|http://pmd.sourceforge.net/pmd-4.3.0/cpd.html] or [simian|http://www.harukizaemon.com/simian/])
> - ...



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)