Parsing the. classpath file under the MyEclipse project

Source: Internet
Author: User
Tags java web

Press CTRL + C to copy the code<classpathentry kind= "src" path= "src"/> <classpathentry kind= "con" path= "org.eclipse.jdt.launching.JRE_ CONTAINER "/> <classpathentry kind=" con "path=" melibrary.com.genuitec.eclipse.j2eedt.core.MYECLIPSE_JAVAEE_5 _container "/> <classpathentry kind=" Lib "path=" Webroot/web-inf/lib/bsf-2.3.0.jar "/> <classpathentry Kin d= "Output" path= "Webroot/web-inf/classes"/> 1. <classpath kind= "src" path= "src" > corresponds to a directory of source folder type, kind---represents this type of classpath, path represents the paths in the project, path uses the relative path of the root directory Path (relative to the. classpath file itself), the SRC in the MyEclipse project is itself a source folder, so it is automatically written to this file, and if you manually create a source folder, the folder will also be written This document, form is the above form of eg. create a new test source folder on the project basis, and it will be like this: <classpathentry kind= "src" path= "src"/> <cla Sspathentry kind= "src" path= "test"/></pre><br> 2. <classpathentry kind= "Con" path= "Org.eclipse.jdt.launching.JRE_CONTAINER"/> This sentence represents the program's operating environment kind= "CON"--- Represents the type of classpath, Con is container, is the container for the program to run, or it is said to be a running ringEnvironment is OK, it is actually in MyEclipse initially to configure the installed JREs specified (typically we specify the JDK), but here is actually using the JRE under the JDK jar package, is jdk_home/jre/ The LIB is the corresponding statement 3. <classpathentry kind= "Con" path= "Melibrary.com.genuitec.eclipse.j2eedt.core.MYECLIPSE_JAVAEE_5_CONTAINER"/ > This sentence is kind= "con", of course, is a container that represents the runtime, typically Java Web projects, it contains a few jar packages to be used by the EE server, the jar package in this directory is the most special, it is not in the deployment project When deployed to the server, because MyEclipse think that such a jar package is the server should have, so there are sometimes problems, there is no problem in development, but after the deployment will be wrong, there are some servers have a jar package is not provided, such as Tomcat (because Tom Cat is not a professional Web server, it is just a lightweight web container, which distinguishes between the development environment and the operating environment 4. <classpathentry kind= "Lib" path= "Webroot/web-inf/lib/bsf-2.3.0.jar"/> This statement kind= "Lib", corresponding to the classpath in the library file, Paths specify the path to the library file, which is also relative to the project root relative to path 5. <classpathentry kind= "Output" path= "Webroot/web-inf/classes"/> This represents the output directory of the project, the entire previously defined classpath either kind= ' src ', Kind= "Con", kind= "Lib", will go into this directory after compilation, in the Java WEB is also webroot/web-inf/classes. The same path that is used is relative to the relative path of the project root (relative to the. classpath file itself), but since the Java EE section itself requires the Web server itself to have those jar packages, the exception is not copied classpath is MyecliPSE important files, the ". Classpath" file that is used in the project root directory when making related lookups is the &LT;CLASSPATH&GT in the file that holds the project classpath. ...</classpath> Save a variety of classpath information, kind represents a type, path represents a route, and uses a relative path relative to the ". Classpath" or the project root directory. kind= "src"----corresponds to Source Folder directory Kind= "Con"--the container of the project, generally, when it is a Java Web project, there will be two kind= "Lib"---the Library files used in the project kind= ' output '--the export directory, the final compilation of the relevant files of the target directory, MyEclipse will automatically complete the relevant copy. Ultimately, the management of MyEclipse classpath is achieved through this filePress CTRL + C to copy the code

. classpath files in the MyEclipse project:<?XML version= "1.0" encoding= "UTF-8"?><Classpath><!--Source Directory -<ClasspathentryKind= "src"Path= "src"/><!--JDK Runtime Container -<ClasspathentryKind= "Con"Path= "Org.eclipse.jdt.launching.JRE_CONTAINER"/><ClasspathentryKind= "Con"Path= "Melibrary.com.genuitec.eclipse.j2eedt.core.MYECLIPSE_JAVAEE_5_CONTAINER"/><!--The following is the path of the class library path for your custom directory, the jar file -<ClasspathentryKind= "Lib"Path= "Webroot/web-inf/lib/sino-base-1.3.2.jar"/><ClasspathentryKind= "Lib"Path= "Webroot/web-inf/lib/sino-bms-1.4.3.jar"/><ClasspathentryKind= "Lib"Path= "Webroot/web-inf/lib/sino-frame-1.2.2.jar"/><!--Output Class directory after compilation -<ClasspathentryKind= "Output"Path= "Webroot/web-inf/classes"/></Classpath>---------------------------------------------------------------------------. project file:<?XML version= "1.0" encoding= "UTF-8"?><projectdescription><!--project name defines the value of the name here if the other items that have worked in the workspace are occupied, when importing the project using the import function of MyEclipse, it will not come in -<name>Sxvip</name><Comment></Comment><Projects></Projects><!--compiler Specifies -<Buildspec>    <Buildcommand>        <name>Org.eclipse.wst.common.project.facet.core.builder</name>        <arguments>        </arguments>    </Buildcommand></Buildspec><!--Core Features -<Natures>    <Nature>Org.eclipse.jem.workbench.JavaEMFNature</Nature>    <Nature>Com.genuitec.eclipse.ast.deploy.core.deploymentnature</Nature>    <Nature>Com.genuitec.eclipse.j2eedt.core.webnature</Nature></Natures></projectdescription>--------------------------------------------------------------------------One more for the MyEclipse project (web Application only). mymetadata File:<?XML version= "1.0" encoding= "UTF-8"?><!--Type : Project type name: Project name ID: Project unique identity within the workspace context-root: site root path J2EE-SPEC:J2EE standard Archi VE: After packaging the war file -<Project-moduletype= "WEB"name= "Upload"ID= "myeclipse.1152954865843"Context-root= "/upload"J2ee-spec= "1.4"Archive= "Upload.war"><attributes>    <!--value:web root directory name -    <attributename= "Webrootdir"value= "WebRoot"/></attributes></Project-module> 
View Code

When you modify the name of a deployment for a myeclipse project,

The value of Context-root in the. mymetedata file changes accordingly

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.