The specific role of the. Project and. classpath files in Eclipse (consolidated):

. Project is a project file, where the structure of the project is defined, such as the location of the Lib, the location of the SRC, the location of the classes

The location of the. CLASSPATH defines the $classpath you use for this project at compile time

These files you can see with a text editor

The purpose of the midpoint refresh in a project is to update the list of files in the. project file so that you display the files that are not submitted to the project through eclipse

      

1<?XML version= "1.0" encoding= "UTF-8"?>2<Classpath>3<ClasspathentryKind= "src"Path= "src"/>4<ClasspathentryKind= "src"Path= "Test"/>5<ClasspathentryKind= "Con"Path= "Org.eclipse.jdt.launching.JRE_CONTAINER"/>6<ClasspathentryKind= "Con"Path= "ORG.ECLIPSE.JDT.JUNIT.JUNIT_CONTAINER/4"/>7<ClasspathentryKind= "Lib"Path= "Lib/dom4j-1.6.1.jar">8<attributes>9<attributename= "Javadoc_location"value= "File:/home/wpc/work/apache/dom4j-1.6.1/docs/api$10 </attributes>11 </classpathentry >12 <classpathentry kind= "Output "Path= "Bin"/> -</Classpath>

View Code

From the data we can easily see that the above describes the project's dependent files:

1. The exact location of the source file (kind= "src")
2. Operating system environment (kind= "con")
3. Specific location information for the project's library (kind= "Lib")
4. In each LIB's XML child node, there is additional configuration information about it (for example, the "Javadoc_location" I configured)
5. Output Directory of the project (kind= "Output")

In general, this document is the configuration of the entire project operating environment.

. project file:

1<?XML version= "1.0" encoding= "UTF-8"?>2<projectdescription>3<name>Createinterpret</name>4<Comment>JavaCC [email protected] 32303037303632392d3130303020437265617465496e746572707265742f777063</Comment>5<Projects>6</Projects>7<Buildspec>8<Buildcommand>9<name>Sf.eclipse.javacc.javaccbuilder</name>Ten<arguments> One</arguments> A</Buildcommand> -<Buildcommand> -<name>Org.eclipse.jdt.core.javabuilder</name> the<arguments> -</arguments> -</Buildcommand> -</Buildspec> +<Natures> -<Nature>Org.eclipse.jdt.core.javanature</Nature> +<Nature>Sf.eclipse.javacc.javaccnature</Nature> A</Natures> at</projectdescription>

View Code

From the data, we can see that these configurations are primarily about describing the basic engineering information:

1. Project Name <name></name>
2. Project Comment Description <comment></comment>
3. Additional Eclipse plug-ins required by the runtime <natures></natures>, and their specific loading method information <buildSpec></buildSpec>

If you add a lot of additional plugins to your project during the development process, it will inevitably cause your eclipse to start slowly.

In this case, you can remove some plugins from the file, but you will be able to load those plugins when you open those associated files.

. settings file:

The configuration files for various plugins are stored inside.

The above is a simple introduction to Eclipse's project-related hidden configuration files.

The specific role of the. Project and. classpath files in Eclipse (consolidated):