You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Petri Tuomola (Jira)" <ji...@apache.org> on 2020/05/08 18:51:00 UTC

[jira] [Commented] (FINERACT-948) Use Gradle Daemon

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

Petri Tuomola commented on FINERACT-948:
----------------------------------------

Definitely worth a try - as far as I can see, this should work with the Cargo plug-in - but of course something else might break...

> Use Gradle Daemon
> -----------------
>
>                 Key: FINERACT-948
>                 URL: https://issues.apache.org/jira/browse/FINERACT-948
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Michael Vorburger
>            Assignee: Michael Vorburger
>            Priority: Major
>             Fix For: 1.4.0
>
>
> With FINERACT-730 having replaced our use of the Gradle Tomcat plugin to Cargo plugin, we should now finally be able to use the (faster...) Gradle daemon mode! 
> I had to disable the Daemon mode, years ago, because Gradle Tomcat plugin wasn't able to shut down the embedded Tomcat cleanly, and it created a mess.  With the Cargo plugin using an externally forked Tomcat, this problem should be gone.
> At least I think we can do this now... it's worth a try. [~ptuomola] feel free to chime in here - especially if you believe that I may have misunderstood how the Cargo plugin differs from the Tomcat plugin. It hopefully does fork Tomcat in an external process - doesn't it?



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