## Factory Component Content

The Factory Component Content wizard page allows you to customize the plug-in data.

Option | Description | Default
--- | --- | ---
Plug-in ID | It is mandatory and it must comply with the plugin.dtd. It must match the factory component project name. | Automatically set, not modifiable
Plug-in Version | It is mandatory and must be of the form major.minor.micro.qualifier. | Default value is set to 1.0.0
Plug-in Name | It is the translatable presentation name of the plug-in. This field is required. | none
Plug-in Provider | It is the translatable name of the plug-in provider. This field is optional. | none
Classpath | It refers to the location of the code once the plug-in is packaged. As of Eclipse 3.1, it is recommended to ship plug-ins as JARs with code at the root of the JAR and leave the classpath field empty. | none
Generate an Activator | An activator is a Java class that controls the plug-in's life cycle. It is only needed if you require to do work upon the startup or shutdown of your plug-in. | The choice of whether the plug-in will make contributions to the UI affects the code generated for the activator: If the plug-in is a UI plug-in, the activator class extends the org.eclipse.ui.plugin.AbstractUIPlugin class. If the plug-in is headless (i.e. non-UI), the activator extends the org.eclipse.core.runtime.Plugin class. If the plug-in is targeted for an OSGi framework, the activator implements the org.osgi.framework.BundleActivator interface.
Factory Component Model | By answering Yes to the question in the Factory Component Model section, you will be required to go to the Templates page where you can choose a template that will generate all the required extensions. | none

Factory Component

TODO

TODO