[
https://issues.apache.org/jira/browse/FINERACT-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17211990#comment-17211990
]
Andres Almiray commented on FINERACT-1198:
------------------------------------------
A good way to start is to run the build with build-cache enabled, that is
activate it ad-hoc with `--build-cache` command flag or set a project property
in `.gradle.properties` as `org.gradle.caching = true`. More information about
local and remote build caches can be found at
[https://docs.gradle.org/current/userguide/build_cache.html].
Next would be to inspect the build's performance, this will require publishing
build scans [https://guides.gradle.org/creating-build-scans/], browse the data
looking for hotspots (cache misses, long running tasks, non cached tasks, etc),
fix, iterate, iterate, iterate.
> Gradle incremental build is broken
> ----------------------------------
>
> Key: FINERACT-1198
> URL: https://issues.apache.org/jira/browse/FINERACT-1198
> Project: Apache Fineract
> Issue Type: Bug
> Components: Build
> Reporter: Michael Vorburger
> Priority: Major
>
> One of the reasons why Gradle is (supposedly) so much cooler than e.g. Maven
> is that it can be really support and support very fast "incremental" builds
> (only rebuild what has changed).
> I have the impression that doesn't really work in Fineract, and suppose
> that's not really Gradle's (core) fault, but some plugin which screws this
> up? OpenJPA Enhancer, SpotBugs... presumably they all have to "play along"
> for this to work perfectly?
> My Gradle foo isn't (nearly) good enough to know if it would be possible to
> "fix" this, and how hard this may be, but filing an issue is perhaps a start
> for getting input from people more knowledgeable about this.
> [~aleks] and/or [~ptuomola] perhaps you have ideas about this.
> [~aalmiray] as per chat during ApacheCon, not sure if this is the kind of
> thing you may enjoy helping with?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
