Classpath effect
Define the structure of the project, such as SRC, output, con, lib, and so on.
The exact location of the source file (kind= "src")
Operating system environment (kind= "con")
Specific location information for the project's library (kind= "Lib")
In each LIB's XML child node, there is additional configuration information about it (for example, the "Javadoc_location" I configured)
Output Directory of the project (kind= "Output")
Sample:
<?xml version= "1.0" encoding= "UTF-8"?>
<classpath>
<classpathentry kind= "src" output= "target/classes" path= "Src/main/java" >
<attributes>
<attribute name= "optional" value= "true"/>
<attribute name= "maven.pomderived" value= "true"/>
</attributes>
</classpathentry>
<classpathentry excluding= "* *" kind= "src" output= "target/classes" path= "Src/main/resources" >
<attributes>
<attribute name= "maven.pomderived" value= "true"/>
</attributes>
</classpathentry>
<classpathentry kind= "src" output= "target/test-classes" path= "Src/test/java" >
<attributes>
<attribute name= "optional" value= "true"/>
<attribute name= "maven.pomderived" value= "true"/>
</attributes>
</classpathentry>
<classpathentry excluding= "* *" kind= "src" output= "target/test-classes" path= "Src/test/resources" >
<attributes>
<attribute name= "maven.pomderived" value= "true"/>
</attributes>
</classpathentry>
<classpathentry kind= "Con" path= "org.eclipse.jdt.launching.jre_container/ org.eclipse.jdt.internal.debug.ui.launcher.standardvmtype/javase-1.6 ">
<attributes>
<attribute name= "maven.pomderived" value= "true"/>
</attributes>
</classpathentry>
<classpathentry kind= "Con" path= "Org.eclipse.m2e.MAVEN2_CLASSPATH_CONTAINER" >
<attributes>
<attribute name= "maven.pomderived" value= "true"/>
</attributes>
</classpathentry>
<classpathentry kind= "Output" path= "Target/classes"/>
</classpath>
. Project makes
Project Name <name></name>
Project Comment Description <comment></comment>
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 get rid of some plugins in this file, but then you will load those plugins when you open those associated files.
Sample:
<?xml version= "1.0" encoding= "UTF-8"?>
<projectDescription>
<name>log4j-jmx-gui</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.m2e.core.maven2Builder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.m2e.core.maven2Nature</nature>
<nature>org.eclipse.jdt.core.javanature</nature>
</natures>
</projectDescription>
Eclipse. Project and. Classpath Effects (RPM)