[
https://issues.apache.org/jira/browse/FINERACT-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212005#comment-17212005
]
Michael Vorburger edited comment on FINERACT-1198 at 10/11/20, 6:43 PM:
------------------------------------------------------------------------
Quick glance at those Scans from a Gradle Noob like me seems to indicate that
even the 2nd build redoes both the :compileJava and :spotlessJava and :resolve
which constitute the bulk of where time is spent. We must be doing something
somewhere which makes it fail to dig that it doesn't have to re-do those.
Perhaps it's the OpenJPA :enhance which touches the class files? Although
hopefully that (should) normally only include {{\*\*/domain/*.class}} (see
build.gradle). But I'm just making stuff up here without a better understand
why those 3 tasks re-run on the 2nd build.
was (Author: vorburger):
Quick glance at those Scans from a Gradle Noob like me seems to indicate that
even the 2nd build redoes both the :compileJava and :spotlessJava and :resolve
which constitute the bulk of where time is spent. We must be doing something
somewhere which makes it fail to dig that it doesn't have to re-do those.
Perhaps it's the OpenJPA :enhance which touches the class files? Although
hopefully that (should) normally only include {{**/domain/*.class}} (see
build.gradle). But I'm just making stuff up here without a better understand
why those 3 tasks re-run on the 2nd build.
> 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
> Assignee: 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)
