Contents
-
Deprecated Classes
since 2.0, the artifact types should be defined by the resolver consumer
-
Deprecated Fields
since 2.0, this property should be defined by the resolver consumer along with the
ArtifactType
implementation
since 2.0, the semantic carried by this property should be defined in a custom
DependencyTraverser implementation provided by the resolver
consumer
since 2.0, the semantic carried by this property and the fact this property is coupled to Resolver
1.x "system" scope (that was delegated to consumer application) implies this property should not be used anymore,
instead, the
ScopeManager exposed via method
RepositorySystemSession.getScopeManager() should be used.
-
Deprecated Methods
This method should not be used. Since version 2 Resolver internally distinguishes between artifact
update policy and metadata update policy. This method was left only to preserve binary compatibility, and in
reality invokes
RepositoryPolicy.getArtifactUpdatePolicy().
-
Deprecated Constructors
This way of creating session should be avoided, is in place just to offer backward binary
compatibility with Resolver 1.x using code, but offers reduced functionality.
Use
RepositorySystem.createSessionBuilder() instead.