You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by "Myrle Krantz (JIRA)" <ji...@apache.org> on 2017/01/12 08:42:52 UTC

[jira] [Commented] (FINERACT-371) Make gradle callable from the top level directory.

    [ https://issues.apache.org/jira/browse/FINERACT-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820494#comment-15820494 ] 

Myrle Krantz commented on FINERACT-371:
---------------------------------------

"branched" this issue out of https://issues.apache.org/jira/browse/FINERACT-357.

Comments relevant to this part of the ticket from there:
[~nazeer1100126] "I believe, integrating RAT on top level directory is unnecessary effort as either we need to duplicate the gradle scripts at top level for RAT only or we need to move the complete source and build scripts from fineract-provider to top level directory."
[~myrle] "2.) I agree with Shaik Nazeer Hussain that providing details in the README is sufficient. What Roman says about lowering the hurdles for reviewers is important, but we also need to keep effort in concordance with benefit. Should we choose to do this point anyways, a possible technical solution is to create a gradle composite build at the top level."

> Make gradle callable from the top level directory.
> --------------------------------------------------
>
>                 Key: FINERACT-371
>                 URL: https://issues.apache.org/jira/browse/FINERACT-371
>             Project: Apache Fineract
>          Issue Type: Wish
>            Reporter: Myrle Krantz
>            Assignee: Markus Geiss
>            Priority: Minor
>
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)