I'm sorry for late response. I'm little bit too busy in the last time. OK, to my question/problem.
Today I'm using Eclipse. And I have in Eclipse a workspace, which is equivalent to a project in IDEA, with 61 projects. Every project has at least 4 source folders: - common (contains classes which should be used by server and by client) - server (contains classes which are only relevant for the server) - client (contains classes which are only relevant for the client) - tests (contains tests for classes in common, server and client)
All of those projects represents a single product.
Some of those 61 projects have up to 3 additional source folders. So if I go and convert all this source folders to modules in IDEA, I will end up with min. 183 modules. And this is a little bit too much for my taste. And I personally prefer to have things which belongs together to have them in a single module instead of splitting them into 3 modules, e.g:
I have currently a Eclipse project named core with the source folders common, server, client. When I migrate it to IDEA, I have to split it into three modules: core-common, core-server, core-client.
BTW. the inability to define an output path per source path in IDEA is the only one difference between Eclipse and IDEA when it comes to defining a project/module. And the only one difference which prevents me from switching from Eclipse to IDEA.
You can split target modules to sub-modules and organize them to module groups.
I.e. I don't see the principal difference between the environments (particular projects have multiple source dirs output paths definitions VS output dir per-module, modules may be assembled to module groups).
Hello Max,
Why do you need this feature? Why can't you break your project into more
modules instead?
--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"
Hello Dmitry,
I'm sorry for late response. I'm little bit too busy in the last time. OK, to my question/problem.
Today I'm using Eclipse. And I have in Eclipse a workspace, which is equivalent
to a project in IDEA, with 61 projects. Every project has at least 4 source folders:
- common (contains classes which should be used by server and by client)
- server (contains classes which are only relevant for the server)
- client (contains classes which are only relevant for the client)
- tests (contains tests for classes in common, server and client)
All of those projects represents a single product.
Some of those 61 projects have up to 3 additional source folders. So if I go and convert all
this source folders to modules in IDEA, I will end up with min. 183 modules. And this is
a little bit too much for my taste. And I personally prefer to have things which belongs together
to have them in a single module instead of splitting them into 3 modules, e.g:
I have currently a Eclipse project named core with the source folders common, server, client.
When I migrate it to IDEA, I have to split it into three modules: core-common, core-server, core-client.
BTW. the inability to define an output path per source path in IDEA is the only one difference
between Eclipse and IDEA when it comes to defining a project/module. And the only one difference
which prevents me from switching from Eclipse to IDEA.
Best regards,
Max Mad
Hi Max,
You can split target modules to sub-modules and organize them to module groups.
I.e. I don't see the principal difference between the environments (particular projects have multiple source dirs output paths definitions VS output dir per-module, modules may be assembled to module groups).
Denis
Hi Denis,
I did not know about this feature. I will give it a try. Maybe it is exactly, what I'm looking for.
Thank you for the tip!
Best regards,
Max Mad