Plugin can not be applied if root project does not have release task about nebula-release-plugin HOT 5 CLOSED

No plans to change this behavior. Designed to release entire directory
together, so root should apply the plugin.
On Sun, Nov 8, 2015 at 5:43 PM Artem Zinnatullin [email protected]
wrote:

Steps to reproduce:

1. Clone RxJava repo https://github.com/ReactiveX/RxJava
2. Create subdir rxjava
3. Move src, build.gradle, gradle.properties to the rxjava folder
4. Change settings.gradle to include ':rxjava'

The problem is that this plugin thinks that rootProject declares release
task, but this is not true for setup when root project is just a container
for subprojects (which is normal and common setup).

project.rootProject.tasks.release.dependsOn(task) in the ReleasePlugin —
is the reason of failure with message: Could not find property 'release' on
task set.

—
Reply to this email directly or view it on GitHub
#33.

from nebula-release-plugin.

But why? :( Do you see some drawbacks of subproject structure? I'm blocked by this in ReactiveX/RxJava#3503.

from nebula-release-plugin.

I think projects with different release cadences should be in different
repositories.

On Mon, Nov 9, 2015 at 2:53 AM Artem Zinnatullin [email protected]
wrote:

But why? :( Do you see some drawbacks of subproject structure? I'm blocked
by this in ReactiveX/RxJava#3503
ReactiveX/RxJava#3503.

—
Reply to this email directly or view it on GitHub
#33 (comment)
.

from nebula-release-plugin.

So

// build.gradle at root of project
allprojects {
  apply plugin: 'nebula.nebula-release'
}

// build.gradle in rxjava subdir
// whatever plugins and dependencies as needed

from nebula-release-plugin.

@rspieldenner applying plugin to allprojects works, thanks!

from nebula-release-plugin.