Java - multi-project - when does it make sense?

Question

Java

Hello, in order to improve my skills, I decided to come up with a task for myself. But at the very beginning the question arose - how best to design?
This is a JavaEE project with all the consequences.
I thought about dividing everything into 3 parts (of the project), maybe I thought wrong, if not, then tell me how it would be better. Why I share, yes, because I want to use different view - technologies.
1. admin panel - view - something from the jsf world, for example PrimeFaces
2. client - view - jsp + jquery
3. database and other utilities that are needed for the admin panel and the client.
Well, in addition to everything, they decided to try instead of the usual maven - gradle.
What exactly is the question.
The question is, do I need a parent object(rootGradle.build)? Or do just 3 separate projects and each has an independent gradle.build?
And if in general - what does such a breakdown into the root and dependent projects give?
Or direct to where a similar topic is discussed or described.
Thank you!

Answer 1

Yes, a root project is needed, unlike maven, there are no links to the parent project in child projects, this scribbling is compensated by a tree-like directory structure.
Create a root project (directory) with your build.gradle (here it is convenient to specify general settings for all projects: common plugins, encoding, repositories, dependencies for logging and testing, jdk version) and settings.gradle (here you list child projects that will be built when root assembly). Next, create projects (root subdirectories) with your own build.gradle and your own specifics.
Useful links:
documentation www.gradle.org/documentation
power of gradle report www.youtube.com/watch?v=NZJTYPLb0iE