Super POM, Parent POM type of hierarchy management in Gradle
gradle
Solution
I do the following:
Define a gradle script (something like a parent pom)
Apply it (something like extending) in my build.gradle file
`apply from: 'https://youUrlHere/parent.gradle'`
For more info, you can have a look here: http://forums.gradle.org/gradle/topics/inheriting_from_a_parent_not_in_the_same_project
Hope this helps.
Problem
We are currently using Maven as our build tool and there is a directive to migrate to Gradle. Our current setup is: - We have a super POM that defines all third party dependencies, various plugins, distributionManagement URLs and this POM is uploaded to our releases repo. - We have an aggregator POM that uses this super POM as parent and aggregates several submodules. - We have several profiles defined in aggregator POM to build components. My question is, what is the best way to do all these in Gradle. How can I define all third party dependencies in a single Gradle config and use it in other places. I am new to Gradle and so, this might sound a very stupid question. But I request all to provide some help and guidance.