Prefacebefore learning the use of the Shiro framework, followed by friends (APE) around the introduction of Git as a local version control (temporarily without GitHub), when using Git to find that git does have a lot of amazing charm, In particular, the management of the branch is best used (although I'm only using it for fast-forward use at the moment). In the process of using git, especially when using the branch conversion process, it was found that eclipse's support for Git and MAVEN support was not very good, and it would cause my entire project to get an error when jumping back to the previous version branch (for example, develop branch (3.3.0) converted back to master ( 3.1.2)), including the following sub-project at the same time the problem. "Project Refresh, Mvn:clean Complie, etc." all useless, can only bite the bullet to the master merge to develop. A friend (also an ape) said: With idea, support for Maven is good. then I fell out of the hole and turned to idea. Behind the discovery idea many concepts and eclipse (I have been using myeclipse) a lot of different places, especially project projects and the relationship between the module, it is difficult to understand, coupled with Maven's parent and module relationship, chaos. Online read a lot of text tutorials are simple explanation:
| Idea |
Eclipse |
| Project |
Workspace |
| Module |
Project |
found still a lot of problems, especially after watching the video of the Youmeek great God, only to know that the network above the understanding is based on eclipse to idea convenient understanding, in order to further study their relationship (do not want to be maven, idea, Eclipse three of the confused force), so went to read the official website article. And be prepared to use your own understanding and translation tools to correspond to the translation again. Novice cat, English is not good, if there is not proper translation of the place please correct me, this translation is not CTRL C + CTRL V, if the words are meaningless.
Official original Addresshttps://www.jetbrains.com/help/idea/2016.1/project.html
This article old cat translation, reprint please add this text connection:http://blog.csdn.net/nthack5730/article/details/51502853
more articles on old cats:http://blog.csdn.net/nthack5730
Recently found some unscrupulous self-proclaimed program learning site with the use of crawler tools to reprint my article (believe that many people have suffered), directly remove all links, make their own writing, too no civic-minded. Reprinted all Right, Link went to nothing, the focus is this reptile turn half not half of, fraught ah! I've checked more than n articles.
Translation:
Project
Directory:
-Basic Knowledge
-Project and file formats
-Directory Basic Format
-File Basic format
basic Knowledge whatever you do in idea, it's about context within the project. A project is an organizational unit that represents a complete solution. The project serves as a support for the basic coding, the majority of refactoring, and the consistency of the coding style. the finished product should be broken down into a series of separate components, separate modules, but this is defined in the project and assembled and bundled together to become a larger whole (not sure if it should be translated as: module assembly can be done through the definition of the project). The project itself does not contain development artifacts such as source code, build scripts, or documents, they are the highest organization in the IDE, they define the project scope settings, and the collection IntelliJ the modules and Lib referenced by idea.
Project and file formats idea saves the project's configuration data and their components in an XML text format, which makes it easier to manage and share the project's configuration data with others. Both of the following formats can store the project's configuration data: Catalog format and file format.
Directory basic format when the directory format is used, a ". Idea" Directory is generated at the root of the project. the ". Idea" directory includes a series of configuration files (. xml format). Each file contains only part of the configuration data, and the name of a file is used to decorate or describe a specific range of functionality, for example: "Compiler.xml,encodings.xml,modules.xml"Almost all files contain the core information of the project itself, such as the name and physical address information of the component module, compiler settings, and so on. Therefore, these files can (and should) be placed under version control. but "Workspace.xml" is the exception. It preserves your personal settings, such as where your idea program is placed, your CVS and history settings, and other data and development environments. So you don't want to share this file with your peers or colleagues.
file basic format when using the file format, there will be two files in your project directory, one of which is the ". IPR" suffix, which holds the core project information, and the other file suffix named ". IWs", which preserves your personal workspace settings. ". IWs" files should not be managed using version control, but ". IPR" should be managed using versioning.
"Basic file format" can be converted to "directory basic format"
, see About: converting Projects into directory-based format.
This article old cat translation, reprint please add this text connection:http://blog.csdn.net/nthack5730/article/details/51502853
more articles on old cats:http://blog.csdn.net/nthack5730
Translation of the official Help document for Idea-project
