Hello,
we’re planning to use gradle for our build processes. We want to provide one Build Project for all our solutions. In case of modularisation and multiple usage of some global functionally we have a project directory like this (using gradle-wrapper):
root
global.gradle
gradlew
gradlew.bat
root/gradle/wrapper
gradle dependencies
root/build/solutionname
build.gradle
some properties and settings
The build.gradle first contains the import of global.gradle:
apply from: '../../global.gradle'
It has cost us some time to figure out how the functions needs to be defined in global.gradle, so we can use them in the other build.gradle files:
ext.foo = { param ->
//do sth
}
in my opinion it’s kinda different to the documentation how you can organize the build logic: Chapter 42. Organizing Build Logic
However, it works for us. My question is now, how own classes in global.gradle can be provided? A class like this is not working:
class Foo {
Foo(param) {
//do sth
}
//functions
}
I’m also open for other solutions to handle the Import. I also tried it like explained here: 42.1. Inherited properties and methods. Unfortunatly that didn’t worked for us.
