Hi everyone, my multi-project android build is usi...

# gradle

[Markus Fung]

Hi everyone, my multi-project android build is using precompiled script plugin for as a convention plugin. Im thinking of migrating to binary plugin. Is there any features or drawbacks in precompiled script plugin compare to binary plugin ?

[Vampire]

Just for readers here too.
As I said in the Gradle slack already, there is no difference in testing either of them.
Both end up as binary plugins and both can be tested exactly the same.
I have no idea why testing should be easier by not using precompiled script plugins.

[Vampire]

precompiled script plugins are just syntactic sugar to build binary plugins more conveniently

[Markus Fung]

sorry for the misinformation. Testing would be the same for precompiled script plugin and binary plugin. Updated that part tho

[hfhbd]

Using binary plugins should be faster due to not compiling the plugins locally.

[Markus Fung]

is there any proof or ways to measure this ? @hfhbd

[hfhbd]

Sure, just use a build scan and compare the compileKotlin etc. of the included build.

[Vampire]

That's not true and also not what he meant

[Vampire]

He talks about precomplied script plugin vs. written as plain old .kt.

[Vampire]

Not included build vs published

[Vampire]

And even then the statement would not be true, as you can as well publish precompiled script plugins the same as you can binary plugins

[Vampire]

As I said, precompiled script plugins are just syntactic sugar to build binary plugins more conveniently.
Whehter you publish or not, whether you use buildSrc or an included build, and so on is all the same.

[hfhbd]

Oh okay, I understand binary (class code) = published. I won’t call kt plugins as binary 😅

[Vampire]

Yeah, that's how Gradle calls them opposed to precompiled script plugins. 🙂

[Markus Fung]

thank you all 🚀