How to organize microservice architecture on Gradle?

Question

Java

I inherited a multi-module Java project.
the structure is as follows:
----------------------
libs service1
--gradle.build.kts
--dockerfile service2
--gradle.build.kts --dockerfile build. gradle.kts settings.gradle.kts versions.gradle.kts docker-compose.yaml ----------------------
The entire project was stored in one bitbacket repository, launched and tested using a common gradle task. The task was to split it into different repositories. We moved the libraries to the corporate Nexus. But how to properly split it into microservices so that single versions of libraries, plugins and tasks of the root build.gradle and versions file are used. Or is the only working option to move the logic of building and versioning libraries into each individual microservice? Or use Git Submodules?

Answer 1

gradle can build one module at a time out of the box "so that you can run it through the CI pipeline without building it entirely":
gradle :service1:build