I remember this is pretty much a desire by any plugin developer so they can have a sibling project that uses/tests the plugin which is my case as well and am hoping 1 of the versions of gradle has a semi-clean possibly hacky way of doing this.
We like the eat our own medicine mantra so for a while now we have been releasing the plugin and then using the PREVIOUS version of the plugin to build the rest of our project. Recently bintray started deprecating their stuff and now our master is broken with this philosophy. I remember a feature came out in Gradle where we could build the plugin in one project and use in another in a single multi-project build. I can’t seem to find the documentation or how to do that.
Any pointers on building and using in the same multi-project build would be fabulous and our build would no longer depend on the remote connection to some artifact repository.
I found this old post which is way too old → Can I develop a Gradle plugin as sibling project in multi project build setup? - #4 by chris_molozian