You mention “modules” and “packages”, and from how you talk about them I suspect you’re talking about Gradle subprojects. With the Kotlin Gradle plugin, you can set different target platforms for each module (usually you’d have several target platforms in one module). You also get to view subprojects in a tree within your project and manage common dependencies in the root project.
You can organize your modules (subprojects) however you like. If you want, you can lay them out the same way as your example.
You were understood me correctly. “Packages” is my mistake.
Thank you for links, that you gave me. Them solved many following problems.
Unexpectedly, modules can be organized with simple directories)
In “Project Structure” I can set dependencies, but not for whole directory. Either directories nothing change in a tree representation. How to fix this?
You probably want to follow the tutorials instead of us copy-pasting each step here–it’ll be a lot easier for you. Although the tutorials may not exactly get you the structure you wrote, following them (and maybe a few Gradle tutorials) will give you the skills to do exactly what you want.
Some of the specific features in 1.4 require you to use the preview release. Luckily there are instructions in the blog post for installing the early access preview.