Eclipse Plug in Development Learning (1)-about the use of Resourcesplugin classes and the addition of plug-in packages in MANIFEST.MF files

Recently, due to some factors, I began to study the development of Eclipse plug in, usually the eclipse development tools from the website to find the corresponding version can be developed

It takes a lot of tools to develop specific projects, but sometimes it's hard to find a third-party plug-in to suit your project's application. So I started the Eclipse development plug-in journey.

The first development of many classes unfamiliar to start looking at data, Chinese information is very difficult to find, but there are many, the process encountered more problems than the information on a few.

Start by documenting some of the problems I've encountered, to find a solution in the future, and to start developing the Eclipse plug-in's children's shoes as well as I do:

The first class you encounter that you can't find is resourcesplugin he exists in a bag called org.eclipse.core.resources.

All articles about developing plug-ins should be mentioned in this class, very important class

However, when generating an Eclipse plug in plug-in project, if you do not do the following, it may not be added directly as an intrinsic expansion package into the project

So, you need to find the Meta-inf folder in your project, open the Manifest.mf file, and check the Dependencies tab page

Modify title for required Plug-ins content, click Add ... button, enter the resources text, he will automatically filter out the package just mentioned, and then save the MANIFEST.MF file

Enter the project source file to use the Resourcesplugin class.

Of course, modifying the libraries of the project adds this jar package to the same effect.

But, MANIFEST. MF also has other functions, that is, when the release of the jar package directly together, the more complete plug-ins will let others pretend to avoid a lot of unnecessary trouble.

Note: There are already org.eclipse.ui packages and org.eclipse.core.runtime packages in MANIFEST.MF, and it is not clear why the Org.eclipse.core.resources package is also added automatically.

Please let me know the cause of the children's shoes, thank you very much.