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

Mua Ndzo Laurent edited comment on FINERACT-765 at 6/14/19 12:37 AM:
---------------------------------------------------------------------

Hi [~vorburger] i am currently rebasing my PR on your work. It was a great 
stuff you did here unblocking stuff. I would remove the task if it is ok. Looks 
like we have got another issue in 
https://issues.apache.org/jira/browse/FINERACT-764 would love to know the way 
forward thanks


was (Author: muarachmann):
Hi [~vorburger] i am currently rebasing my PR on your work. It was a great 
stuff you did here ublocking stuff. I would remove the task if it is ok. Looks 
like we have got another issue in 
https://issues.apache.org/jira/browse/FINERACT-764 would love to know the way 
forward thanks

> Remove Flyway completely from Gradle build, and run it only in-App at runtime
> -----------------------------------------------------------------------------
>
>                 Key: FINERACT-765
>                 URL: https://issues.apache.org/jira/browse/FINERACT-765
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Michael Vorburger.ch
>            Priority: Major
>
> In https://github.com/apache/fineract/pull/582 for FINERACT-761 for 
> https://github.com/apache/fineract/pull/525 for FINERACT-700, [~vishwasbabu] 
> raised an interesting point:
> {quote}@vorburger : Thinking back, we could probably have simply removed all 
> the flyway tasks from gradle. I am not sure if anybody was actually using 
> them (the gradle tasks for migrating DB's listed in the readme are not really 
> required as flyway would run anyway on application startup){quote}
> IFF nobody actually has to use those tasks during the build, then removing 
> them would be a very welcome simplification! 
> It's technically not "needed" for the Gradle upgrade in FINERACT-700 in the 
> very short term, because after MUCH pain we've sorted the Flyway related 
> issues out, but this still seems a very worthwhile simplifcation to ease 
> future pain.
> I wouldn't have time for this, but perhaps someone would like to pick this up?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to