stream-chat-android VS publish-plugin

Nothing, but that hardly achieves the same thing. For example, if you're building an API that others will consume and you want to let them dynamically replace parts of the UI within your components, you'll have quite a challenge giving your users a simple and flexible API based on Views (see for example many things in Stream's SDK that I used to work on). Gets even more difficult if this is within a RecyclerView.

So that's the implementation we ended up with for now! You can find all of this code in the Chat Android SDK's GitHub repository if you want to look at it in a real project.

Check out Stream on Github. They have a few chat SDKs for iOS, Android, React and a few others. Website: https://getstream.io/

We’ll use our very own Android Chat SDK in our examples. This SDK is made up of multiple artifacts, but for simplification, we’ll just talk about publishing the low-level networking client, which lives in the stream-chat-android-client module of the GitHub repository.

We already ship a UI Components library in our Chat SDK which contains ready-to-go, fully-featured Android Views to drop into your app, along with ViewModels that let you connect them to business logic in just a single line of code. You can check out how that works in our Android Chat Tutorial.

To easily automate publishing later, you'll use the gradle-nexus/publish-plugin tool. This has to be added in your project level (root) build.gradle file as a dependency.

There is a remedy: Gradle Nexus Publish Plugin. This plugin automatically closes and releases OSSRH staging repositories whenever you publish something. To use it, remove the repositories section from the publishing plugin configuration of your build script (the one mentioning "OSSRH" in my example above) and add these lines to your build:

Yeah, the new plugin which combines both of these functionalities is wip https://github.com/gradle-nexus/publish-plugin . I assume this will get released soon.