Mutli-project problems with build order and gradle-release plugin


(Peter Kahn) #1

Hi all,

Using net.researchgate.release and a subproject dependency project(":projectA") results in projectB dependency on projectA NEXT-SNAPSHOT not RELEASE-VERSION.

It looks like gradle-release plugin processes release steps for parent, then subproject A, then subproject B. The order is great, but it means that when release steps executed for subproject B it relies on next snapshot for A and not the release version.

I’ve tried executing the build is steps (A, B, parent) but still get the problem.

Is there a way to inject a version into the dependency or is there a way to enforce build order without that :project dependency?

ProjectB Build.Gradle
dependencies { compile project(":projectA")