BuildPath in Eclipse "reprint"

What is build Path?

The Build path is a collection of resource properties that specifies the Java project contains.

In a mature Java project, not only the source code, but also the System Runtime Library (JRE), the third-party function extension Library, other works in the workspace, and even the external class files, all of these resources are dependent on this project, and only after being referenced, To be able to compile the project successfully, and build path is used to configure and manage references to these resources.

The Build path typically includes:

1. JRE Runtime Library
2. Third-party feature Extensions library (*.jar format files)
3. Other projects
4. Other source or class files

Why use build Path?

By using build Path, you can better manage the resources contained in the Java project and make the engineering structure clear and reasonable.
Conversely, with the increase in code and functionality, the engineering structure becomes disorganized and difficult to manage.

specific content in Eclipse is described in:

To open the Build Path management interface:
Right-click on Project->build path->configure Build Path

Projects options: You can add, edit, and remove items that the current project depends on.

Libraries Options: You can add, edit, and remove library files that the current project depends on.
Add JARs: Is the jar file that is added in the current project directory.
Add External JARs: is a jar file in an external directory that is added outside the current project.
Add Variable: is a variable added.
Add Library: is the repository for adding JRE systems.
Add Class Folder: Adds the. class file that is compiled in the current project.
Add External class Folder: Adds A. class file other than the current project.

Order and export: You can sort the libraries that are already added to the current project, or you can set whether the library files also follow the project export when the current project is exported.

Attention:
1. After you change the version of the system library of the project, the problem is that the later version of the revision is changed to the lower version, and the lower version is not a problem to the higher version.
Because some of the packages in the higher-version system libraries are not present in the lower version of the library. Therefore, the compatibility of the lower version of the system library is good.

2. After changing the version of the system library for the project, if it is a later version, change the compatibility option of the JDK to the current version of the JDK. However, it is not a problem if the lower version of the system library is changed to a higher version without changing the compatibility of the JDK.
Because JDK compatibility uses the JDK version associated with the version of the JRE that we chose when we created the project.
The reason that the lower version of the system library is changed to a higher version is that the JDK compatibility is not changed because the higher version of the JDK is compatible with the lower version.

BuildPath in Eclipse "reprint"