The following points of view are personal understanding, no practice, and subsequent realization.
Ideas:
1, Eclipse and myeclipse, idea these development tools to create their own projects, have their own set of ideas, the project structure has its own characteristics.
2. If these development tools are imported into the project, they should be modified according to the project structure of the respective development tools, and spend a lot of effort.
3, if the members of the group use the development tools are not unified, is also a problem, or the project history brought about the development tools are not unified, is also a problem.
Solution Ideas:
1, the introduction of MAVEN to build the project.
MAVEN has a standard set of built-in catalogs that can be imported and identified by the development tools of Eclipse and myeclipse and idea, regardless of their new project.
It solves the problem of non-unification of the member development tools in the group, and uses whatever it wants to use.
Secondly, our project is ultimately built with MAVEN to build the output, so, regardless of the development tools, it will eventually output the MAVEN-standard project structure.
Create a new project structure that is compatible with Eclipse and myeclipse, idea