Deprecated API
Contents
-
ClassDescriptionsince 2.0, the artifact types should be defined by the resolver consumerDefinition and semantics of the scopes should be defined by consumer project.The use of class should be avoided, see
StringDigestUtil
and file processor in SPI module.This class is deprecated. Use same named class from impl module instead.This class is deprecated. Use same named class from impl module instead.This class belongs to consumer project. Resolver should have no notion of scopes.This class belongs to consumer project. Resolver should have no notion of scopes.This class belongs to consumer project. Resolver should have no notion of scopes.UseConfigurableVersionSelector
instead.since 2.0, the DependencyTraverser implementation should be provided by the resolver consumerSeePostorderDependencyNodeConsumerVisitor
that is more versatile.SeePreorderDependencyNodeConsumerVisitor
that is more versatile.
-
FieldDescriptionsince 2.0, this property should be defined by the resolver consumer along with the
ArtifactType
implementationsince 2.0, the semantic carried by this property should be defined in a customDependencyTraverser
implementation provided by the resolver consumersince 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, theScopeManager
exposed via methodRepositorySystemSession.getScopeManager()
should be used.
-
MethodDescriptionUse
Artifact.getPath()
instead.UseArtifact.setPath(Path)
instead.UseUpdateCheck.getPath()
instead.UseUpdateCheck.setPath(Path)
instead.UseTrackingFileManager.read(Path)
instead.UseTrackingFileManager.update(Path, Map)
instead.UseMergeableMetadata.merge(Path, Path)
instead.UseMetadata.getPath()
instead.UseMetadata.setPath(Path)
instead.UseLocalArtifactResult.getPath()
instead.UseLocalArtifactResult.setPath(Path)
instead.UseLocalMetadataResult.getPath()
instead.UseLocalMetadataResult.setPath(Path)
instead.UseLocalRepository.getBasePath()
instead.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 invokesRepositoryPolicy.getArtifactUpdatePolicy()
.UseRepositoryEvent.Builder.setPath(Path)
instead.UseRepositoryEvent.getPath()
instead.UseArtifactResult.addException(ArtifactRepository, Exception)
method instead.UseArtifactTransfer.getPath()
instead.UseArtifactTransfer.setPath(Path)
instead.UseMetadataTransfer.getPath()
instead.UseMetadataTransfer.setPath(Path)
instead.UseGetTask.getDataPath()
instead.UseGetTask.setDataPath(Path)
instead.UseGetTask.setDataPath(Path, boolean)
instead.UsePutTask.getDataPath()
instead.UsePutTask.setDataPath(Path)
instead.UseTransferResource.getPath()
instead.Use SPI checksum selector instead.Use SPI checksum selector instead.Use SPI FileProcessor to read and write checksum files.Resolver is oblivious about "scopes", it is consumer project which needs to lay these down and also assign proper semantics. Moreover, Resolver is oblivious about notions of "classpath", "modulepath", and any other similar uses. These should be handled by consumer project.Resolver is oblivious about "scopes", it is consumer project which needs to lay these down and also assign proper semantics. Moreover, Resolver is oblivious about notions of "classpath", "modulepath", and any other similar uses. These should be handled by consumer project.UseNodeListGenerator.getPaths()
instead.
-
ConstructorDescriptionThis 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.UseLocalRepository(Path)
instead.UseLocalRepository(Path, String)
instead.UseArtifactUpload(Artifact, Path)
instead.UseMetadataDownload(Metadata, String, Path, String)
instead.UseMetadataUpload(Metadata, Path)
instead.Use constructor that provides consumer application specific predicate.Use constructor that provides consumer application specific predicate.Use constructor that provides consumer application specific predicate.