This message was deleted.

What you are after are composite builds. With that you can include a whole build in another build and then the artifacts coming from the included build are automatically built and used from source instead of the version in the respository. No need to use the broken-by-design local maven repository or deploying it somewhere else. Also the IDE will then open the sourcecode together properly and enable you to work on both sources at the same time and do refactorings and so on.

So if I read that correctly, I would create a build.gradle.kts in a separate (probably non-version-controlled) project which includes all the builds of the projects that I want to work on together. And each developer creates their own project like this?

That's one way. You can also have some magic in your settings script like "if the project X is checked out at relative place Y, include the build". Or you can make it dependent on some property that a developer can set in his

gradle.properties

in

GRADLE_USER_HOME

, and so on.

But one basically empty project that includes all the other ones is an okay thing to do?

Sure, should also work fine if you prefer it that way.

Okay, thank you again 🙂