Home >> All >> org >> eclipse >> pde >> [ core Javadoc ]

•

org.eclipse.pde.core.build.* (4)

•

org.eclipse.pde.core.plugin.* (22)

• org.eclipse.pde.core: Javadoc index of package org.eclipse.pde.core.


Package Samples:

• org.eclipse.pde.core.plugin
• org.eclipse.pde.core.build

Classes:

• ISharedPluginModel: This type of model is created by parsing the manifest file. It serves as a base interface for both plug-in and fragment models by holding data common to both. If the file is a workspace resource, it will be available as the underlying resource of the model. The model may be read-only or editable. It will also make a reference to the build.properties model when created. The reference will be of the same type as the model itself: if the model is editable, it will attempt to obtain an exclusive editable copy of build.properties model. The plug-in model can be disabled. Disabling the model will not ...
• IPluginModelBase: This type of model is created by parsing the manifest file. It serves as a base interface for both plug-in and fragment models by holding data common to both. If the file is a workspace resource, it will be available as the underlying resource of the model. The model may be read-only or editable. It will also make a reference to the build.properties model when created. The reference will be of the same type as the model itself: if the model is editable, it will attempt to obtain an exclusive editable copy of build.properties model. The plug-in model can be disabled. Disabling the model will not ...
• IExtensionsModel: This type of model is created by parsing the manifest file. It serves as a base interface for both plug-in and fragment models by holding data common to both. If the file is a workspace resource, it will be available as the underlying resource of the model. The model may be read-only or editable. It will also make a reference to the build.properties model when created. The reference will be of the same type as the model itself: if the model is editable, it will attempt to obtain an exclusive editable copy of build.properties model. The plug-in model can be disabled. Disabling the model will not ...
• IFragmentModel: This type of model is created by parsing the fragment.xml file. If the file is a workspace resource, it will be available as the underlying resource of the model. The model may be read-only or editable. It will also make a reference to the plugin.jars model when created. The reference will be of the same type as the model itself: if the model is editable, it will attempt to obtain an exclusive editable copy of plugin.jars model. The fragment model can be disabled. Disabling the model will not change its data. Users of the model will have to decide if the disabled state if of any importance to them ...
• IPluginModel: This type of model is created by parsing the plugin.xml file. If the file is a workspace resource, it will be available as the underlying resource of the model. The model may be read-only or editable. It will also make a reference to the plugin.jars model when created. The reference will be of the same type as the model itself: if the model is editable, it will attempt to obtain an exclusive editable copy of plugin.jars model. The plug-in model can be disabled. Disabling the model will not change its data. Users of the model will have to decide if the disabled state if of any importance to them ...
• IModelProvider: Classes that implement this interface are responsible for holding a table of models associated with the underlying objects. They have several responsibilities: To hold model objects in one place To allow requesters to connect to the models or to disconnect from them. To maintain reference count of model users. To ensure "one writer/many readers" access to the model so that only one requester can get an editable copy of the model at any time. To notify interested parties when models are added and removed. Model providers are responsible for listening to the workspace, updating models whose underlying ...
• IModel: A generic model. Classes that implement this interface are expected to be able to: Load from an input stream Reload (reset, load, fire 'world change') Dispose (clear all the data and reset) Be associated with a resource (optional) If a model is not created from a workspace resource file, its underlying resource will be null .
• IBuildModel: This model is created from the "plugin.jars" file that defines what source folders in the plug-in are to be used to build require plug-in Jars. If this model is editable, isEditable() will return true and the model instance will implement IEditable interface. The model is capable of providing change notification for the registered listeners.
• IEditable: Models that implement this interface indicate that they can be changed. When a model is changed, it becomes 'dirty'. This state can either be reset (in case of a 'false alarm' or naturally set to false as a result of saving the changes. Models that implement this interface are expected to be able to save in ASCII file format (e.g. XML).
• IModelProviderListener: Classes should implement this interface in order to be able to register as model provider listeners. They will be notified about events such as models being added or removed. These changes are typically caused by the changes in the workspace when models are built on top of workspace resources.
• IEditableModel: Editable model is an editable object that can be saved. The classes that implement this interface are responsible for calling the method save of IEditable and supplying the required PrintWriter object.
• IModelChangeProvider: Classes that implement this interface are capable of notifying listeners about model changes. Interested parties should implement IModelChangedListener and add as listeners to be able to receive change notification.
• IBaseModel: A base generic model. Classes that implement this interface are expected to be able to: Dispose (clear all the data and reset) Tell if they are editable Tell if they contain valid data
• IExtensions: A model object that contains the portion of the plug-in model responsible for extensions and extension points. If the plug-in contains OSGi manifest file, plugin.xml is reduced to extensions and extension points only.
• IMatchRules: This interface contains constants used throughout the plug-in for plug-in reference matching. These rules are used to control when determining if two compared versions are equivalent.
• IPluginReference: Object that implement this interface represent references of plug-ins. Plug-ins are referenced using their identifiers, and optionally versions and match rules.
• IModelChangedEvent: Model change events are fired by the model when it is changed from the last clean state. Model change listeners can use these events to update accordingly.
• ISourceObject: This interface indicates that a model object is created by parsing an editable source file and can be traced back to a particular location in the file.
• IModelChangedListener: Classes that need to be notified on model changes should implement this interface and add themselves as listeners to the model they want to listen to.
• IPluginBase: A model object that represents the content of a plug-in or fragment manifest. This object contains data that is common for bo plug-ins and fragments.
• ISharedExtensionsModel: This type of model is created by parsing the plug-in manifest file but only takes the extensions and extension points into account.
• IWritable: Classes that implement this interface can participate in saving the model to the ASCII output stream using the provided writer.
• IModelProviderEvent: This event will be delivered to all model provider listeners when a model managed by the model provider changes in some way.
• IPluginLibrary: The class that implements this interface represents a reference to the library that is defined in the plug-in manifest.
• IPluginExtension: Classes that implement this interface model the extension element found in the plug-in or fragment manifest.

Home | Contact Us | Privacy Policy | Terms of Service