| Home >> All >> org >> eclipse >> update |
Package Samples:
• org.eclipse.update.standalone
• org.eclipse.update.search
• org.eclipse.update.operations
• org.eclipse.update.internal.security
• org.eclipse.update.internal.search
• org.eclipse.update.internal.operations
• org.eclipse.update.internal.model
• org.eclipse.update.internal.mirror
• org.eclipse.update.internal.core
• org.eclipse.update.core.model
• org.eclipse.update.core
• org.eclipse.update.configuration
• org.eclipse.update.ui
• org.eclipse.update.internal.ui.wizards
• org.eclipse.update.internal.ui.parts
• org.eclipse.update.internal.ui.model
• org.eclipse.update.internal.ui
• org.eclipse.update.internal.ui.preferences
• org.eclipse.update.internal.ui.properties
• org.eclipse.update.internal.ui.security
Classes:
• IFeatureContentProvider: Feature content provider. A feature content provider is an abstraction of each feature internal packaging structure. It allows the feature content to be accessed in a standard way regardless of the internal packaging. All concrete feature implementations need to implement a feature content provider. There are two ways of looking at a feature content: the "logical" view, which is a representation of the actual files that make up the feature. These include any files that describe the feature itself, files that are the actual implementation of referenced plug-ins, and files that are the non-plug-in ...
• IFeatureContentConsumer: Feature content consumer. A feature content consumer is an abstraction of each feature internal packaging mechanism. It allows content to be stored into a feature in a standard way regardless of the packaging mechanism used. Only concrete features that support storing need to implement a content consumer. The platform implements at least one feature type supporting content consumer. This is the feature type representing a locally-installed feature. A feature content consumer delegates the storage of plug-in and non-plug-in files to a generic content consumer. Clients may implement this interface. ...
• IFeature: Feature defines the packaging "container" for a group of related plug-ins, plug-in fragments, and optionally non-plug-in files. Features are treated purely as an installation and packaging construct. They do not play a role during Eclipse plug-in execution. They are simply an inclusive "manifest" of the plug-ins, fragments and other files that make up that feature. If features are logically made up of plug-ins from "sub-features", the top-level feature "manifest" must be fully resolved at packaging time. Clients may implement this interface. However, in most cases clients should directly instantiate ...
• INonPluginEntry: Non-plug-in entry defines an arbitrary non-plug-in data file packaged as part of a feature. Non-plug-in entries are not interpreted by the platform (other than being downloaded as part of an install action). They require a custom install handler to be specified as part of the feature. Note, that defining a non-plug-in entry does not necessarily indicate the non-plug-in file is packaged together with any other feature files. The actual packaging details are determined by the feature content provider for the feature. Clients may implement this interface. However, in most cases clients should directly ...
• IInstallHandler: Custom install handler. Custom install handlers can optionally be associated with a feature. The actual install handler implementation can be physically delivered as part of the feature package, or can already be installed on the client machine and registered via the org.eclipse.update.core.installHandlers extension point. The install handler methods are called at predetermined point during update actions. Clients may implement this interface. However, in most cases clients should directly subclass the provided implementation of this interface. Note: This class/interface is part of an interim API ...
• ICategory: Feature category definition. A site can organize its features into categories. Categories can be further organized into hierarchies. Each category name is a composed of the name of its parent and a simple identifier separated by a slash ("/"). For example tools/utilities/print defines a category that is a child of tools/utilities and grandchild of tools . Clients may implement this interface. However, in most cases clients should directly instantiate or subclass the provided implementation of this interface. Note: This class/interface is part of an interim API that is still under development and ...
• UpdateSearchRequest: This class is central to update search. The search pattern is encapsulated in update search category, while the search scope is defined in the scope object. When these two objects are defined and set, search can be performed using the provided method. Search results are reported to the result collector, while search progress is tracked using the progress monitor. Classes that implement IUpdateSearchResultCollector should call 'filter' to test if the match should be accepted according to the filters added to the request. Note: This class/interface is part of an interim API that is still under development ...
• IPluginEntry: Plug-in entry defines a packaging reference from a feature to a plug-in. It indicates that the referenced plug-in is to be considered as part of the feature. Note, that this does not necessarily indicate that the plug-in files are packaged together with any other feature files. The actual packaging details are determined by the feature content provider for the feature. Clients may implement this interface. However, in most cases clients should directly instantiate or subclass the provided implementation of this interface. Note: This class/interface is part of an interim API that is still under ...
• IPlatformEnvironment: Plug-in entry defines a packaging reference from a feature to a plug-in. It indicates that the referenced plug-in is to be considered as part of the feature. Note, that this does not necessarily indicate that the plug-in files are packaged together with any other feature files. The actual packaging details are determined by the feature content provider for the feature. Clients may implement this interface. However, in most cases clients should directly instantiate or subclass the provided implementation of this interface. Note: This class/interface is part of an interim API that is still under ...
• ListenersList: This class is used to maintain a list of listeners, and is used in the implementations of several classes within JFace which allow you to register listeners of various kinds. It is a fairly lightweight object, occupying minimal space when no listeners are registered. Note that the add method checks for and eliminates duplicates based on identity (not equality). Likewise, the remove method compares based on identity. Use the getListeners method when notifying listeners. Note that no garbage is created if no listeners are registered. The recommended code sequence for notifying all registered listeners ...
• IVerificationResult: Verification result. An object implementing this interface represents a token passed between the update framework and the verifier and verification listener. The verifier uses the token to capture the result of the file verification. It is then passed to the verification listener to optionally present this information to the user (in an implementation-specific way). The verification listener in turn uses this token to capture the desired response. Clients may implement this interface. Note: This class/interface is part of an interim API that is still under development and expected to change significantly ...
• IPlatformConfiguration: Platform configuration interface. Represents the runtime configuration used by the Eclipse platform. Any configuration changes do not take effect until next startup of the Eclipse platform. Do not provide implementations of this interface or its nested interfaces. Use the factory methods on IPlatformConfigurationFactory to create a IPlatformConfiguration, then use the factory methods on the IPlatformConfiguration to create instances of ISiteEntry,IFeatureEntry and ISitePolicy. Note: This class/interface is part of an interim API that is still under development and expected to change significantly ...
• FeatureHierarchyElement: This class is used to construct a joint feature hiearchy. Old feature reference represents feature that is found on in the current configuration. New feature reference is found in the feature that is an install/update candidate. The element is used to join nodes of the hiearchy formed by including features so that each node in the hiearchy contains references to the old and the new feature. Old and new features have the same IDs but different versions, except in the case of optional features, where the tree may be constructed to bring in an optional feature that was not installed initially. In ...
• ISiteContentProvider: Site content provider. A site content provider is an abstraction of each site internal organization. It allows the site content to be accessed in a standard way regardless of the internal organization. All concrete site implementations need to implement a site content provider. Clients may implement this interface. However, in most cases clients should directly instantiate or subclass the provided implementation of this interface. Note: This class/interface is part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made ...
• PlatformConfiguration: This class is responsible for providing the features and plugins (bundles) to the runtime. Configuration data is stored in the configuration/org.eclipse.update/platform.xml file. When eclipse starts, it tries to load the config info from platform.xml. If the file does not exist, then it also tries to read it from a temp or backup file. If this does not succeed, a platform.xml is created by inspecting the eclipse installation directory (its features and plugin folders). If platform.xml already exists, a check is made to see when it was last modified and whether there are any file system changes ...
• ISiteFactoryExtension: This is an extension to the standard ISiteFactory interface. If a factory implements this interface and is handling URL connections, a progress monitor can be passed to allow canceling of frozen connections. Input stream is obtained from the connection on a separate thread. When connection is canceled, the thread is still active. It is allowed to terminate when the connection times out on its own. Note: This class/interface is part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit ...
• IURLEntry: URL entry is an annotated URL object. It allows descriptive text to be associated with a URL. When used as description object, the annotation typically corresponds to short descriptive text, with the URL reference pointing to full browsable description. Clients may implement this interface. However, in most cases clients should directly instantiate or subclass the provided implementation of this interface. Note: This class/interface is part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage ...
• IArchiveReference: Site archive interface. Site archive is a representation of a packaged archive (file) located on an update site. It allows a "symbolic" path used to identify a plug-in or non-plug-in feature entry to be explicitly mapped to a specific URL. Clients may implement this interface. However, in most cases clients should directly instantiate or subclass the provided implementation of this interface. Note: This class/interface is part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit ...
• BaseFeatureFactory: Base implementation of a feature factory. The factory is responsible for constructing the correct concrete implementation of the model objects for each particular feature type. This class creates model objects that correspond to the concrete implementation classes provided in this package. The actual feature creation method is subclass responsibility. This class must be subclassed by clients. Note: This class/interface is part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit ...
• BaseSiteFactory: Base implementation of a site factory. The factory is responsible for constructing the correct concrete implementation of the model objects for each particular site type. This class creates model objects that correspond to the concrete implementation classes provided in this package. The actual site creation method is subclass responsibility. This class must be subclassed by clients. Note: This class/interface is part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback ...
• ISite: Site represents a location containing some number of features (packaged or installed). Sites are treated purely as an installation and packaging construct. They do not play a role during Eclipse plug-in execution. Clients may implement this interface. However, in most cases clients should directly instantiate or subclass the provided implementation of this interface. Note: This class/interface is part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering ...
• IImport: Plug-in dependency entry. Describes a feture dependency on a particular plug-in. The dependency can specify a specific plug-in version and a matching rule for satisfying the dependency. Clients may implement this interface. However, in most cases clients should directly instantiate or subclass the provided implementation of this interface. Note: This class/interface is part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding ...
• IUpdateSearchSite: This interface is used to represent sites that need to be searched within the search scope. In addition to being an update site adapter, it also returns an array of categories within the site that need not be searched (skipping categories makes the search faster because fewer features need to be checked and potentially downloaded from the server). Note: This class/interface is part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding ...
• IVerificationListener: Verification listener. This interface abstract the user interaction that may be required as a result of feature installation. In particular, as feature archives are downloaded and verified, the user may need to indicate whether to accept any one of the archives, or abort the installation. Clients may implement this interface. Note: This class/interface is part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code ...
| Home | Contact Us | Privacy Policy | Terms of Service |