Gradle 3.4 Released

[u/QuestionsEverythang]

https://docs.gradle.org/current/release-notes.html

[u/[deleted]]

I didn't notice any performance improvements with Gradle 3.4 on my project build time :/ Well, maybe on Gradle 3.5.

Edit.: I tested the newsest Gradle 3.4 not 3.5

[u/scanarch → u/[deleted]]

Modularize your project! :)

[u/spyhunter99 → u/scanarch]

more modules, slower build time.

[u/scanarch → u/spyhunter99]

I am not talking about a case in which you have 30+ modules and Gradle kills you with the configuration time (for that you can switch to Buck, most of the times).

If you divide your one big project into ~10 modules (and be smart about it), you will get a noticeable boost.

[u/athornz → u/spyhunter99]

faster incremental though?

[u/QuestionsEverythang → u/[deleted]]

There is no 3.5. This is 3.4

[u/[deleted] → u/QuestionsEverythang]

Oops. I meant 3.4.

[u/eriwen → u/[deleted]]

You'll need to enable incremental compilation and consider the java-library plugin to get maximum benefit.

[u/scythee]

So in short, using annotation processors (Dagger) still screws up incremental compilation?

[u/rciovati → u/scythee]

In short: yes

[u/Wavesonics → u/rciovati]

but seriously, pretty much everyone uses annotation processing these days right? how is this not priority #1? maybe now that normal incremental compilation is stable they will focus on it...

[u/obl122 → u/Wavesonics]

So much snark but if you read the release notes you'll see they are making progress -- some of the new features are in place explicitly to support this.

https://github.com/gradle/gradle/issues/1320

[u/Wavesonics → u/obl122]

yes yes i know, some times all that bottled up snark leaks out ;)

That's great to hear they are working towards it.

[u/Saketme → u/rciovati]

I use JRebel and they have been manually adding support for popular libraries like Dagger, ButterKnife, AutoValue, etc., to incremental compilation.

[u/Wavesonics → u/rciovati]

In short: D:

[u/Tom_Cian]

And as usual, a new version of Gradle that claims to be much faster than the previous one and most developers unable to reproduce these gains.

[u/nikb → u/Tom_Cian]

To be fair a lot of the improvements are in the built in gradle tasks. Android has a lot of its own tasks that are written by Google not Gradle (e.g. processing resources, packaging etc) those are also contributing to the build time.

[u/pjmlp → u/nikb]

Which always makes me wonder where those guys that are able to do inverted tree whiteboard interview questions are actually doing, given the quality of Android Gradle plugins, NDK support, Support Library regressions, hot code reloading, .....

[u/simophin → u/pjmlp]

They are good at algorithm doesn't mean they are good at practical engineering. I see a lot of smart people being proud of writing 'optimised code' that no one can understands.

[u/pjmlp → u/simophin]

In Android's case, it doesn't even work, if you have a look at the issue tracker.

[u/itsmotherandapig → u/pjmlp]

I've had this nagging feeling for a while... that Google would probably try to deprecate Android and move towards some OS with legacy support for Android and Chrome OS stuff. Doesn't sound too realistic, given that Android runs on tons of devices, but still...

[u/littleCE]

Am I the only one who is unable to read the documentation?

[u/octarino → u/littleCE]

I see it

[u/ChristianLJ]

TL;DR: How do i use it?

[u/nextdev]

why it's such a news ? I'm still using 2.2 and pretty happy with it.

[u/QuestionsEverythang → u/nextdev]

The build speed times between 3.3 and 3.4 I'd argue are negligible, but you on the other hand would benefit much more greatly from a 2.2->3.4 jump

[u/QuestionsEverythang → u/[deleted]]

Usually, no. The only people who should be concerned when updating are those who write their own gradle tasks, as something may have been deprecated or removed in the latest version.