Package org.gradle.api.artifacts.result
Interface ResolutionResult
public interface ResolutionResult
Contains the information about the result of dependency resolution. You can use this type to determine all the component instances that are included
 in the resolved dependency graph, and the dependencies between them.
- 
Method SummaryModifier and TypeMethodDescriptionvoidallComponents(Closure closure) Applies given closure for each component.voidallComponents(Action<? super ResolvedComponentResult> action) Applies given action for each component.voidallDependencies(Closure closure) Applies given closure for each dependency.voidallDependencies(Action<? super DependencyResult> action) Applies given action for each dependency.Retrieves all instances ofResolvedComponentResultfrom the graph, e.g.Set<? extends DependencyResult> Retrieves all dependencies, including unresolved dependencies.The attributes that were requested.getRoot()Gives access to the root of resolved dependency graph.Returns the root of resolved dependency graph as aProviderofResolvedComponentResult.The root variant of the dependency graph.
- 
Method Details- 
getRootResolvedComponentResult getRoot()Gives access to the root of resolved dependency graph. You can walk the graph recursively from the root to obtain information about resolved dependencies. For example, Gradle's built-in 'dependencies' task uses this to render the dependency tree.- Returns:
- the root node of the resolved dependency graph
 
- 
getRootComponentProvider<ResolvedComponentResult> getRootComponent()Returns the root of resolved dependency graph as aProviderofResolvedComponentResult. The returnedProvideris live, and tracks the producer tasks of this resolution result. The provider will resolve the component metadata as required. You can walk the graph recursively from the root to obtain information about resolved dependencies. For example, Gradle's built-in 'dependencies' task uses this to render the dependency tree.- Returns:
- a provider for the root component of the resolved dependency graph
- Since:
- 7.4
 
- 
getRootVariantThe root variant of the dependency graph. This is a synthetic variant that represents the thing being resolved. All outgoing dependencies of this variant represent first-level declared dependencies of the resolution.- Returns:
- a provider for the root variant of the dependency graph.
- Since:
- 8.11
 
- 
getAllDependenciesSet<? extends DependencyResult> getAllDependencies()Retrieves all dependencies, including unresolved dependencies. Resolved dependencies are represented by instances ofResolvedDependencyResult, unresolved dependencies byUnresolvedDependencyResult. In dependency graph terminology, this method returns the edges of the graph.- Returns:
- all dependencies, including unresolved dependencies.
 
- 
allDependenciesApplies given action for each dependency. An instance ofDependencyResultis passed as parameter to the action.- Parameters:
- action- - action that is applied for each dependency
 
- 
allDependenciesApplies given closure for each dependency. An instance ofDependencyResultis passed as parameter to the closure.- Parameters:
- closure- - closure that is applied for each dependency
 
- 
getAllComponentsSet<ResolvedComponentResult> getAllComponents()Retrieves all instances ofResolvedComponentResultfrom the graph, e.g. all nodes of the dependency graph.- Returns:
- all nodes of the dependency graph.
 
- 
allComponentsApplies given action for each component. An instance ofResolvedComponentResultis passed as parameter to the action.- Parameters:
- action- - action that is applied for each component
 
- 
allComponentsApplies given closure for each component. An instance ofResolvedComponentResultis passed as parameter to the closure.- Parameters:
- closure- - closure that is applied for each component
 
- 
getRequestedAttributesAttributeContainer getRequestedAttributes()The attributes that were requested. Those are the attributes which are used during variant aware resolution, to select the variants. Attributes returned by this method are desugared, meaning that they have lost their rich types and can only be of type Boolean or String.- Since:
- 5.6
 
 
-