From commits-return-7465-archive-asf-public=cust-asf.ponee.io@fineract.apache.org Tue Mar 3 11:06:16 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id B31CE180651 for ; Tue, 3 Mar 2020 12:06:15 +0100 (CET) Received: (qmail 50033 invoked by uid 500); 3 Mar 2020 11:06:15 -0000 Mailing-List: contact commits-help@fineract.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fineract.apache.org Delivered-To: mailing list commits@fineract.apache.org Received: (qmail 50024 invoked by uid 99); 3 Mar 2020 11:06:15 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Mar 2020 11:06:15 +0000 From: GitBox To: commits@fineract.apache.org Subject: [GitHub] [fineract] xurror opened a new pull request #716: FINERACT-696 - add spotbug bug-pattern plugin. Message-ID: <158323357506.12918.4332077225081737425.gitbox@gitbox.apache.org> References: In-Reply-To: Date: Tue, 03 Mar 2020 11:06:15 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit xurror opened a new pull request #716: FINERACT-696 - add spotbug bug-pattern plugin. URL: https://github.com/apache/fineract/pull/716 add spotbug bug-pattern plugin. closes https://issues.apache.org/jira/browse/FINERACT-696 ## Description While code reviewing https://github.com/apache/fineract/pull/464, I came accross a catch & printStackTrace, which is of course wrong (it should instead be, correctly, logged, instead). In an ideal world, it would not take human code review to catch this, but just an automated build failure. This is possible using SpotBugs (not FindBugs anymore; SpotBugs is the new FindBugs, it's a fully compatible successor) and https://github.com/KengoTODA/findbugs-slf4j/ (for this particular case https://github.com/KengoTODA/findbugs-slf4j/issues/70, but using findbugs-slf4j for Fineract would have value even before that's implemented). ## Checklist Please make sure these boxes are checked before submitting your pull request - thanks! - [ ] Commit message starts with the issue number from https://issues.apache.org/jira/projects/FINERACT/. Ex: FINERACT-646 Pockets API. - [ ] Coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions have been followed. - [ ] API documentation at https://github.com/apache/fineract/blob/develop/api-docs/apiLive.htm has been updated with details of any API changes. - [ ] Integration tests have been created/updated for verifying the changes made. - [ ] All Integrations tests are passing with the new commits. - [ ] Submission is not a "code dump". (Large changes can be made "in repository" via a branch. Ask on the list.) Our guidelines for code reviews is at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org With regards, Apache Git Services