The. classpath,. project files, and. settings files in the Eclipse engineering directory

1. Classpath defines the $classpath you use for this project at compile time (note: Each time you update the jar version or add jar, submit the. classpath file in SVN, otherwise the build of the project A jar that does not already exist in the jar of Path)

<?xml version= "1.0" encoding= "UTF-8"? ><classpath><classpathentry kind= "src" path= "src"/>< Classpathentry kind= "src" path= "resource"/><classpathentry exported= "true" kind= "con" path= " Org.eclipse.jst.j2ee.internal.module.container "/><classpathentry exported=" true "kind=" con "path=" ORG.ECLIPSE.JDT.JUNIT.JUNIT_CONTAINER/4 "/><classpathentry kind=" con "path=" org.eclipse.jdt.launching.JRE_ CONTAINER "/><classpathentry kind=" Lib "path=" Webroot/web-inf/lib/xmlbeans-2.6.0.jar "/>< Classpathentry kind= "Lib" path= "Webroot/web-inf/lib/xmlschema-1.4.7.jar"/><classpathentry kind= "Output" path = "Build/classes"/></classpath>

Configuration in eclipse determines the contents of the. classpath file

　

2. Project file Records project information

<?XML version= "1.0" encoding= "UTF-8"?><projectdescription>    <name>Bonc_ioc_omp</name> <!--project name ---    <Comment></Comment> <!--project Description --    <Projects>    </Projects>    <Buildspec>        <Buildcommand> < Check options!--build Project --            <name>Org.eclipse.wst.jsdt.core.javascriptValidator</name>            <arguments>            </arguments>        </Buildcommand>        <Buildcommand>            <name>Org.eclipse.jdt.core.javabuilder</name>            <arguments>            </arguments>        </Buildcommand>        <Buildcommand>            <name>Org.eclipse.wst.common.project.facet.core.builder</name>            <arguments>            </arguments>        </Buildcommand>        <Buildcommand>            <name>Org.eclipse.wst.validation.validationbuilder</name>            <arguments>            </arguments>        </Buildcommand>        <Buildcommand>            <name>Com.genuitec.eclipse.j2eedt.core.DeploymentDescriptorValidator</name>            <arguments>            </arguments>        </Buildcommand>        <Buildcommand>            <name>Com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder</name>            <arguments>            </arguments>        </Buildcommand>    </Buildspec>    <Natures> <!--load eclipse comes with a plugin--        <Nature>Com.genuitec.eclipse.ast.deploy.core.deploymentnature</Nature>        <Nature>Org.eclipse.jem.workbench.JavaEMFNature</Nature>        <Nature>Org.eclipse.wst.common.modulecore.ModuleCoreNature</Nature>        <Nature>Org.eclipse.wst.common.project.facet.core.nature</Nature>        <Nature>Org.eclipse.jdt.core.javanature</Nature>        <Nature>Org.eclipse.wst.jsdt.core.jsNature</Nature>    </Natures></projectdescription>

The setting of the Buildcommand option is determined by the settings at

3, Settings folder record the basic settings of the project, such as code, the JDK version used, the file compiled JDK version and other information

The. classpath,. project files, and. settings files in the Eclipse engineering directory