You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@fineract.apache.org by "Yemdjih Kaze Nasser (Jira)" <ji...@apache.org> on 2020/07/06 03:24:00 UTC

[jira] [Assigned] (FINERACT-1079) Run Task spotlessApply before compileJava?

     [ https://issues.apache.org/jira/browse/FINERACT-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yemdjih Kaze Nasser reassigned FINERACT-1079:
---------------------------------------------

    Assignee: Awasum Yannick

> Run Task spotlessApply before compileJava?
> ------------------------------------------
>
>                 Key: FINERACT-1079
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1079
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Awasum Yannick
>            Assignee: Awasum Yannick
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> Developers consistently have problems manually running the spotlessApply task after coding changes... See: [https://github.com/apache/fineract/pull/1151] and [https://github.com/apache/fineract/pull/1148]
> maybe we should just run spotlessApply just before compilation and skip the tasks to check for spotless failures? Or we run both of them: Run spotlessApply before spotlessCheck (seems wasteful). Is this a good idea? I wonder?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)