i encountered something funny with gradle plugins ...

# gradle

[Nikky]

i encountered something funny with gradle plugins yesterday, only applying a plugin to a subproject caused it to use a unsupported gson version, adding the plugin to the rootProject with apply false and removing the version information from the subProjects plugin block fixed it.. and i have no clue why and whats going on there

[gildor]

Maybe some other plugin applied on root project adds old gson to dependencies graph

[Nikky]

but thats the interestig bit, the location or order of the plugins makes no difference, unless it adds gson in some delayed fashion

[Nikky]

it can be declared as last plugin in the rootProject and still works or first plugin in the subproject and break