Deprecated API
Contents
-
Deprecated Interfaces
-
Deprecated ClassesClassDescriptionsince 2.0, the artifact types should be defined by the resolver consumer(To be removed as it was introduced in 2.0.0-alpha-2!) This class is wrong, as it uses Resolver 1.x bits that do interpret dependency scopes. The proper session supplier should be provided by consumer project (Maven) that also defines the dependency scopes and their meaning and semantics, as session need to be equipped with these bits. Session is very much dependent on the consumer project.Definition and semantics of the scopes should be defined by consumer project.The use of class should be avoided, see
StringDigestUtiland file processor in SPI module.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.since 2.0, the DependencyTraverser implementation should be provided by the resolver consumerSeePostorderDependencyNodeConsumerVisitorthat is more versatile.SeePreorderDependencyNodeConsumerVisitorthat is more versatile.
-
Deprecated FieldsFieldDescriptionsince 2.0, this property should be defined by the resolver consumer along with the
ArtifactTypeimplementationsince 2.0, the semantic carried by this property should be defined in a customDependencyTraverserimplementation 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, theSystemScopeHandlerexposed via methodRepositorySystemSession.getSystemScopeHandler()should be used.To be removed when deprecated constructors are removed.
-
Deprecated MethodsMethodDescriptionUse
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.
-
Deprecated ConstructorsConstructorDescriptionThis 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.