Uses of Interface
org.eclipse.equinox.p2.engine.IProfile
Packages that use IProfile
Package
Description
Provides support for interacting with the p2 provisioning engine
Provides queries specific to profiles
Provides support for registering new provisioning actions and touchpoints.
Provides core support for interacting with a dependency resolution mechanism.
-
Uses of IProfile in org.eclipse.equinox.p2.engine
Methods in org.eclipse.equinox.p2.engine that return IProfileModifier and TypeMethodDescriptionIProfileRegistry.addProfile
(String id) Add the given profile to this profile registry.IProfileRegistry.addProfile
(String id, Map<String, String> properties) Add the given profile to this profile registry.IProfileRegistry.getProfile
(String id) Return the profile in the registry that has the given id.IProfileRegistry.getProfile
(String id, long timestamp) Return the profile in the registry that has the given id and timestamp.IProvisioningPlan.getProfile()
Returns the profile that this plan will operate on.IProfile[]
IProfileRegistry.getProfiles()
Return an array of profiles known to this registry.Methods in org.eclipse.equinox.p2.engine with parameters of type IProfileModifier and TypeMethodDescriptionIEngine.createPlan
(IProfile profile, ProvisioningContext context) Creates a provisioning plan whose methods can be use to provide pre-validated changes.boolean
Check if the given profile from this profile registry is up-to-date. -
Uses of IProfile in org.eclipse.equinox.p2.engine.query
Methods in org.eclipse.equinox.p2.engine.query with parameters of type IProfileModifier and TypeMethodDescriptionstatic boolean
UserVisibleRootQuery.isUserVisible
(IInstallableUnit iu, IProfile profile) Test if theIInstallableUnit
, in the context of aIProfile
is visible to the user -
Uses of IProfile in org.eclipse.equinox.p2.engine.spi
Methods in org.eclipse.equinox.p2.engine.spi with parameters of type IProfileModifier and TypeMethodDescriptionThis method is called at the end of an engine operation after all phases have been executed and after the touchpoint has had prepare called.Touchpoint.completeOperand
(IProfile profile, Map<String, Object> parameters) This method is called at the end of processing of a single engine operand (for example a given installable unit being installed or uninstalled).Touchpoint.completePhase
(IProgressMonitor monitor, IProfile profile, String phaseId, Map<String, Object> parameters) This method is called at the end of execution of an engine phase.Touchpoint.initializeOperand
(IProfile profile, Map<String, Object> parameters) This method is called at the beginning of processing of a single engine operand (for example a given installable unit being installed or uninstalled).Touchpoint.initializePhase
(IProgressMonitor monitor, IProfile profile, String phaseId, Map<String, Object> parameters) This method is called at the beginning of execution of an engine phase.This method is called at the end of an engine operation after all phases have been executed but prior to the operation being formally committed/persisted.This method is called at the end of an engine operation after all phases have been executed. -
Uses of IProfile in org.eclipse.equinox.p2.planner
Methods in org.eclipse.equinox.p2.planner with parameters of type IProfileModifier and TypeMethodDescriptionIPlanner.createChangeRequest
(IProfile profileToChange) IPlanner.getDiffPlan
(IProfile currentProfile, IProfile targetProfile, IProgressMonitor monitor)