问题
I am working on a project which it's environment initialized in eclipse and has been built in eclipse. There were no lack of performance in loading and running of project. We decided to migrate or environment on a maven base platform. Due to number of sub modules of project(around 400 sub modules), loading of project become a nightmare. So what is the solution in this kind of situation?
回答1:
Divide your 400-module-project into smaller projects following one of the following approaches - depending on the organisation of your development environment:
1) Divide by business domains aspects
Is there functionality that can be seen as self-contained? E.g. user/access control, master data management, accounting, reporting, etc. If there is such those are good candidates for separate projects.
Example:
+- your-application
+- commons
+- ... functionality/tools used by all others ...
+- access-control
+- ... access control modules ...
+- master-data
+- ... master data modules ...
+- accounting
+- ... accounting modules ...
+- reporting
+- ... reporting modules ...
+- ...
+ ...
2) Divide by technical aspects
Your "one data access layer, one business layer and one presentation layer" are good candidates for separate projects.
Example:
+- your-application
+- commons
+- ... functionality/tools used by all others ...
+- data-access
+- ... your data access modules ...
+- business
+- ... your business layer modules ...
+- presentation
+- ... your presentation layer modules ...
3) A combination of the two above
Example:
+- your-application
+- commons
+- ... functionality/tools used by all others ...
+- access-control
+- data-access
+- business
+- presentation
+- integration-tests
+- master-data
+- data-access
+- business
+- presentation
+- integration-tests
+- ...
+- accounting
+- data-access
+- business
+- presentation
+- integration-tests
+- ...
+- reporting
+- data-access
+- business
+- presentation
+- integration-tests
+- ...
+- ...
+ ...
来源：https://stackoverflow.com/questions/30681024/massive-maven-project