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

Juhan Aasaru commented on FINCN-173:
------------------------------------

My ideas how this could be implemented in 3 steps. In any way it is a lot of 
work but it would prove very valuable.

* It would be easy to upgrade to Gradle 4.1 at first as it seems it is 
compatible with current version (just need to change verison number). I made 
some POC-s with 4.1:

[https://travis-ci.com/aasaru/fineract-cn-anubis/builds/128919199]

[https://travis-ci.com/aasaru/fineract-cn-provisioner/builds/128893799]

Then I think as next step it would make sense to update to latest Gradle 4.x. 
The problems seems to be with Gradle versions after 4.1 that the boot 
publification is not picked up.

Lastly I would upgrade from latest Gradle 4.x to Gradle 5.x. 
dependency-management-plugin is not compatible with Gradle 5.x as it has its 
own dependency resolution.

 

> Upgrade all fineract-cn-* repos to latest Gradle 5.x
> ----------------------------------------------------
>
>                 Key: FINCN-173
>                 URL: https://issues.apache.org/jira/browse/FINCN-173
>             Project: Fineract Cloud Native
>          Issue Type: Improvement
>            Reporter: Juhan Aasaru
>            Priority: Major
>
> Proposed by [~Kwesi] to update gradle build scripts to latest version.
> This should be done with all fineract-cn-* repos (including libraries) 
> together - meaning that once the work has been completed all the pull 
> requests to every single fineract-cn-* github repo would be merged together.
>  



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

Reply via email to