Multi-project setup: `release.dependsOn` configuration should not be mandatory about gradle-release-plugin

[netzwerg]

Could you please give more details on how it is failing?
A minimal

plugins {
  id 'ch.netzwerg.release' version '1.0.0'
}
apply plugin: 'java'

works for me.

[etiennestuder]

I do not have the java plugin applied to the project where I have the release plugin applied. I have a multi-project setup, applying the release plugin to the root project (which is otherwise pretty empty). The java plugin is only applied to the sub-projects.

[netzwerg]

Thanks, Etienne. I can reproduce it in a multi-project setup and will fix it asap.

[netzwerg]

I have just committed a fix which resolves the issue for my test setup. Please give it a spin and let me know whether it works for you.

Multi-project task resolution is beyond my limited Gradle knowledge -- if you see potential for improvement, a PR would be highly appreciated!

[etiennestuder]

I will try it out. Though, I must say that the 'afterEvaluate' approach does not fit well when you need the processed version available sooner than that.

[netzwerg]

I have reverted my fix because the approach of manually adding a build task will not work in Gradle 3.0 (as announced here).

Will have to think about an alternative solution...

[netzwerg]

As a workaround, please add release.dependsOn subprojects.build to your root project (after the subprojects block). I will mention this in the README until I have found a proper fix.