-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi-project setup: release.dependsOn
configuration should not be mandatory
#19
Comments
Could you please give more details on how it is failing?
works for me. |
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. |
Thanks, Etienne. I can reproduce it in a multi-project setup and will fix it asap. |
release.dependsOn
configuration should not be mandatory
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! |
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. |
…of multi-project setup" This approach will not be supported in Gradle 3 This reverts commit ec4e541.
I have reverted my fix because the approach of manually adding a Will have to think about an alternative solution... |
As a workaround, please add |
A release block without setting the 'dependsOn' property fails the build
The text was updated successfully, but these errors were encountered: