Creating a plug-in project (II)
26 January 2008Review the first part of this post first.
On the Plug-in Content page, you set the data with which the plugin.xml file will be initialized, including the plug-id, version and name.
The recommended deployed form of a plug-in is to be shipped as a single JAR with all the classes and resources at the root of the JAR. For this format, you may keep the Classpath field empty, or enter ‘.’ (without quotes).
The Plug-in class is a top-level Java class that represents the entire plug-in. It will be used at runtime to control the plug-in’s life cycle, i.e. its implementation will determine what happens when the plug-in starts up or shuts down.
Click Next.
The next page shows the various templates that PDE provides which generate useful content such as views, editors, property pages etc.
In this example, we will create a plug-in with the “Hello, World” template. You can read about the wizard in the area to the right of the wizard list.
Click Next.
The next page will let you customize the sample extension that we are creating.
When you press Finish, the wizard will create the new project, all the specified folders and files, and the initial Java build path. The build path is important for correct compilation of Java classes that are generated. The wizard will also open the plug-in manifest editor.
After the wizard is finished, the initial project structure should look like this:
Related Posts:
- Creating a plug-in project (I)
- Creating a Simple Plug-in using PDE (I)
- Creating a Simple Plug-in using PDE (II)
- Plugin project - Dependencies page (II)
- Eclipse Plug-in Development Environment (I)
- Plugin project - Overview page
- Plug-in manifest editor
- Documenting projects
- Eclipse Plug-in Development Environment (II)
- PDE concepts (I)
Top Of Page | Trackback
If you found this page useful, consider linking to it. Simply copy and paste the code below into your web site.
It will look like this: Creating a plug-in project (II)
