I try to migrate a Maven multi-project build to gradle and I had a look at the "multi-project build" guide and to be honest, it is not really useful. I don't care about multi language build, but the most important and certainly the first thing we need to setup in multi project build is the dependency management and plugin management, and I can't see it.
In my opinion, it would be quite interesting to have such hierarchy:
<project_name>
|- <module_a> (kotlin library)
|- <module_b> (kotlin library)
|- <module_x> (aggregator)
|- <module_x_1> (kotlin library)
|- <module_x_2> (kotlin application)
|- <module_y> (aggregator)
|- <module_y_1> (kotlin library)
|- <module_y_2> (kotlin application)
Where dependencies and plugins versions are factorised in the <project_name> module.
A concrete, real life example.
Cheers.
I try to migrate a Maven multi-project build to gradle and I had a look at the "multi-project build" guide and to be honest, it is not really useful. I don't care about multi language build, but the most important and certainly the first thing we need to setup in multi project build is the dependency management and plugin management, and I can't see it.
In my opinion, it would be quite interesting to have such hierarchy:
<project_name>
|- <module_a> (kotlin library)
|- <module_b> (kotlin library)
|- <module_x> (aggregator)
|- <module_x_1> (kotlin library)
|- <module_x_2> (kotlin application)
|- <module_y> (aggregator)
|- <module_y_1> (kotlin library)
|- <module_y_2> (kotlin application)
Where dependencies and plugins versions are factorised in the <project_name> module.
A concrete, real life example.
Cheers.