In the Eclipse plug-in development process, in order to better maintain and manage the plug-in project build path, it is best to convert the previous simple jar package into Eclipse's plug-in package, if it belongs to the Open source class library, we can obtain its source code files, in eclipse can and allow Easy to view and track source files, but sometimes we also get hints from source not found, such as:
In a situation like this, if you have the source code, you can create a new source code plug-in, so you can directly view the source code files, otherwise you can only think of other ways, such as installing a reverse-compiled plug-in, but sometimes it seems to be a bad compile, processing constants will be messy, and there is no Javadoc file, Here I will explain the source code plug-in production.
We create a new Lib folder in our project and then put Dbutil.jar and related jar packages into this folder, double hit the manifest.mf file in the Meta-inf folder and switch to the Runtime tab. In the lower right corner of the Classpath group, click the "Add" button, the Lib directory to add the jar file to the plug-in build path, and then in the "exported Packages" group, click the "Add" button, the jar file Java package Export to other plug-in projects can be referenced. Here is a screenshot:
This is basically done, we can modify the general information of Plug-ins, such as the plug-in version of the good, plug-in bundle name, said, add corresponding dependencies, where we use the dbutil-2.4.4 version of the MANIFEST.MF file, we modify the overview tab corresponding Information: