You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Michael Vorburger (Jira)" <ji...@apache.org> on 2020/10/20 16:10:00 UTC

[jira] [Commented] (FINERACT-931) Test and Document Spring Boot Dev Tools for (automatic "hot reloading" like restarts in development)

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

Michael Vorburger commented on FINERACT-931:
--------------------------------------------

I'm toying with this today; WIP on [https://github.com/apache/fineract/compare/develop...vorburger:FINERACT-931_boot-devtools].

Eclipse Java Build Path for {{src/main/java}} needs to be manually changed from {{bin/main}} to {{build/classes/java/main}}, and {{src/main/resources}} also from {{bin/main}} to {{build/classes/java/main}}, and the {{build/classes/java/main/resources}} source folder in Eclipse (which only contains the generated {{git.properties}} needs to be removed - then this seems to basically work! It's pretty cool...

To turn my branch into a PR and recommend this more widely, we would have to make above "just work". How do we automate this with Gradle? Do we want to; do we see any downside to "mixing" the "Gradle CLI" and the "Eclipse IDE" classpath? I've been a proponent of keeping this separate in the past myself, but here it actually seems useful..

FINERACT-1228 is a minor side effect I've noticed (not blocking).

Or... do we not need / want this, because "just" basic JVM hot code replacement in debug mode is good enough? (I know it's not the same, the question is if we want to go this way, or close this issue.) Then perhaps we could document that more clearly?

> Test and Document Spring Boot Dev Tools for (automatic "hot reloading" like restarts in development)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: FINERACT-931
>                 URL: https://issues.apache.org/jira/browse/FINERACT-931
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Michael Vorburger
>            Assignee: Michael Vorburger
>            Priority: Critical
>              Labels: beginner, technical
>             Fix For: 1.5.0
>
>
> FINERACT-730 unlocks the Spring Framework's "hot" reloading for development.
> We should test that, and document it in the README.



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