A brief discussion on workspace configuration file of MyEclipse

These days when testing a project with JUnit, read the spring configuration file, always read it, and always use eclipse to see how it manages the classpath of the project.

version: MyEclipse 8.0

First, when we create a new workspace, we will create a new one in the new workspace directory. Metadata, we call this new workspace the W bar. This folder is basically put in the eclipse of the W this work area of some basic configuration, I think we can modify some eclipse under W configuration will eventually write to this folder to touch a file, so that eclipse in the next time we enter the W before our settings will remain valid, It also shows that we're creating a new workspace. Then the previous settings are useless and should read not a. metadata file.

Say more, first look at the directory of the. Metadata folder.

The. Metadata directory has 2 folders and 3 files, and 2 folders are . Me_tcat and. Plugins, both of which can guess what the name is. The Me_tcat folder is the published directory of the MyEclipse comes with Tomcat, When you get in, you'll find Tomcat familiar folders WebApps

Yes, we used MyEclipse's own tomcat to publish Web projects here, and. Plugins look at the name can also guess is the storage of some plug-ins

Configuration file, that is, some of the settings we made, so did not go into the drill. Next look at the remaining 3 files, namely . Lock,. Log, Version.ini, the first of the. lock file does not know what to do, open is a blank, the Internet to check the next did not find, have time to look at the officer online, the following said . log this file, This file is more important, to see the name is recorded in the log, the record is myeclipse error message, I once was through this log file to solve a myeclipse problem, Version.ini see the name is a record version. All right, metadata's done. We're talking about a new workspace case, after a while you'll find the. bak_0.log,. bak_1.log files, this is a backup of the log.

Now that we've created a simple project and entered the new project folder, we've found a . Settings folder and. Classpath,. Project two files, the. Settings contains information about the project, such as the Java version. Here's the. Classpath, open you'll get a general idea of Eclipse's classpath-related issues. This file has these several properties

<classpathentry excluding= "*.txt" kind= "src" path= "src"/> King represents a kind, path is a route

king= "src" indicates that the directory under path refers to the source code

King= "con" means the jar package for Eclipse,

King= "Lib" means third-party jar packages that our developers use in their projects

King= "Var" is also used by the developer Project Jar package, and Lib is different from the Var path has java_home such as defined in the Classpath, and Lib's path is the absolute path used, such as c:/myjar/ Jdbc.jar

king= "Output" indicates the path of the compiled class input.

Excluding indicates that the file under this path that conforms to the value after excluding is not included in the classpath.

All right, I'm probably done.

Today, I encountered an eclipse read jar package error problem, the impact is that I use myeclipse when the use of alt+/when the old play a box, very depressed, and finally found to see Look at the. log file to know that a jar read and write failed, found the jar package found that the jar has been damaged, a re-down, OK problem solved.

MyEclipse Workspace configuration file