not able to resolve gradle plugin dependecy - app.cash.redwood.build

[vikaspw]

I have added treehouse library in my project and added schema but not able to add plugin - app.cash.redwood.build which is required to auto generate the code for widget and interface for my schema.
Please help

[vikaspw]

to be specific not able to resolve schema module plugin-
apply plugin: 'app.cash.redwood.schema'
I have cheked in the redwood repo you have replaced witl local ref
includeBuild('build-support') {
dependencySubstitution {
substitute module('app.cash.redwood.build:gradle-plugin') using project(':')
substitute module('app.cash.redwood:redwood-gradle-plugin') using project(':redwood-gradle-plugin')
}
}
how to do this while adding redwood/treehouse as library in real project?

[JakeWharton]

You should not be using app.cash.redwood.build plugin, that is our internal plugin that manages our own conventions and is not published (because it doesn't make sense for use by anyone except us).

For app.cash.redwood.schema you need the app.cash.redwood:redwood-gradle-plugin dependency added. We add it here:

redwood/build.gradle

Line 13 in 09a3c27

classpath 'app.cash.redwood:redwood-gradle-plugin'

In a real project you would specify the latest released version. We don't do that because we need to build against the version inside the repo itself.

[vikaspw]

@JakeWharton @swankjesse Now i am facing issue in while using as library in presenter-treehouse module-
redwoodBuild {
ziplineApplication('emoji-search')
}
not able to find redwoodBuild .. what should i use ?

[vikaspw]

@JakeWharton @swankjesse I am facing lot of issues while making sample as and using treehouse as library.
do you guys having sample which usages redwood treehouse as library?

[JakeWharton]

You do not need to use anything from the redwoodBuild plugin. It is our build convention plugin local to this repo only.

That specific function, ziplineApplication, is used to embed the Zipline files for the Treehouse application inside the APK so that we can run our automated tests without needing a remote or local server hosting them.

The README has instructions for running the local development server, although you need to comment out that ziplineApplication line in the build for the development server to work because of #1820.

In production we have a dedicated CDN that we upload the Zipline files to, and then we use a feature flag to tell the applications which version to download from the CDN. None of that code is public, but we talk about in either this talk or this one (which were given back-to-back).

[vikaspw]

@JakeWharton I am little confused .. can we use KMM library insider presenter like viewmodel, navigation..?