To fix the issue you can do The main reasons to have a multi-module project is to manage dependencies (in the maven sense) between the different modules (and build them together in the right order). Your microservices may call each other, but are not dependent on each other in the Maven sense. So I would not use multi-module projects for them. Nevertheless, you can define a parent pom for your microservices that defines common configuration and dependencies.
it fixes the issue You can actually do all of this manually with minimal fuss. In the Package Explorer view, right-click on your src folder and choose "Build Path" -> "Remove from Build Path" Underneath the src folder, create a main/java folder Right-click on the main/java folder and choose "Build Path" -> "Use as Source Folder" Repeat steps 2 and 3 for test/java Using the Eclipse refactoring tools (right-click on a folder or file and choose "Refactor" -> "Move…", move your Java files to the new folders
Run all microservices in a multi-project gradle build
I wish this helpful for you If you run a task on the root project, Gradle invokes the same task (if it exists) on all the subprojects. Just execute runApp from the root folder. In your case however, your runApp task might not exit because it starts a server, so execution will not move on to the next project. You can either enable parallel execution, or modify your tasks to run your server tasks in the background (using ProcessBuilder)
Microservices: Should I arrange my spring project structure by entities or by MVC pattern structure?
To fix this issue The answer to your question is very contextual and may differ in different organizations. However, it really boils down on which one is easier for you to manage and how complex is your application. Going for case 1 means that it will be easier to find related components together. However, it becomes difficult to manage entities that mean different in different contexts (User in authentication can be a buyer in a retail shop).
How to use Afterburner.fx with Gradle instaed of Maven 3, while leaving the original project structure of afterburner.fx