[
https://issues.apache.org/jira/browse/FINERACT-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104749#comment-17104749
]
Awasum Yannick commented on FINERACT-821:
-----------------------------------------
[~Collins]. Pick something else from the backlog to work on. [~Manthan] is
claiming this one for this GSoC work. Next time [~Manthan] , dont wait for
someone to show interest on an issue before you self assign to yourself. Pick
one or 2 issues at a time to work on and give room for others. You can go
through the issue tracker and pick the issues you are interested in...so that
people dont get confused. One person should own and work on a single issue in
most cases.
> Enable and enforce (!) Checkstyle in Fineract
> ---------------------------------------------
>
> Key: FINERACT-821
> URL: https://issues.apache.org/jira/browse/FINERACT-821
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Michael Vorburger
> Assignee: Manthan Surkar
> Priority: Major
> Fix For: 1.4.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> as suggested in FINERACT-712, we really should enable Checkstyle in Fineract.
> My past experience in such matters, confirmed by FINERACT-702, is that these
> things only ever work and have a lasting effect if you bulk fix all
> violations and switch on enforcement. If you only report, it's mostly useless.
> As for specific Checkstyle rules, I have spent a fair amount of time in a
> past life on a project (which I'm currently no longer actively invoved in) to
> refine a what I believe to be "good" Checkstyle rule set, we could reuse this
> for Fineract (it's EPL licensed, so copy/pasting it is perfectly fine), see
> https://github.com/opendaylight/odlparent/blob/master/checkstyle/src/main/resources/odl_checks.xml
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
