Before we run the new view, let's take a look at the manifest file that was generated for us:
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin
id="com.example.helloworld"
name="Helloworld Plug-in"
version="1.0.0"
provider-name="EXAMPLE"
class="com.example.helloworld.HelloworldPlugin">
<runtime>
<library name="helloworld.jar">
<export name="*"/>
</library>
</runtime>
<requires>
<import plugin="org.eclipse.ui"/>
<import plugin="org.eclipse.core.runtime"/>
<import plugin="org.eclipse.core.runtime.compatibility"/>
</requires>
<extension
point="org.eclipse.ui.views">
<category
name="Hello Category"
id="com.example.helloworld">
</category>
<view
name="Hello View"
icon="icons/sample.gif"
category="com.example.helloworld"
class="com.example.helloworld.HelloWorldView"
id="com.example.helloworld.HelloWorldView">
</view>
</extension>
</plugin>
The information about the view that we provided when we created the plug-in project was used to generate a manifest file with the appropriate mark-up for defining our view extension. In the extension definition, we define a category for the view, including its name and id. We then define the view itself, including its name and id, and we associate it with the category using the id we defined for our category. We also specify the class that implements our view, HelloWorldView.
As you can see, the manifest file wraps up all the information about our extension and how to run it into a nice, neat package.