nebula-plugins / nebula-plugins/nebula-release-plugin
Issue With Gradle 7.3 - Multiprojects
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 236
- Forks
- 60
- Avg merge
- 10m
- Merged PRs (30d)
- 4
Description
If I create a multiproject-build structure from scratch with gradle 7.3
and I apply the "nebula.release" plugin in a build.gradle file that is NOT located in the root folder I get this error:
What went wrong:
An exception occurred applying plugin request [id: 'nebula.release']
Failed to apply plugin 'nebula.release'.
Task with name 'release' not found in root project 'bea'.
As a workaround I create a build.gradle in the root folder and apply this plugin to it here.
This is actually a pain, since I wanted to work with the precompiled scrip plugins (bea.java-common-conventions.gradle) to have a common convention for the project configuration.
Greetings
Tony
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the multiproject setup with Gradle 7.3 and the nebula.release plugin applied from a non-root build.gradle. Compare that setup with the precompiled script plugin bea.java-common-conventions.gradle and the root-project workaround. Done means the plugin applies successfully from the convention script without requiring a root build.gradle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100