Deprecated API
Contents
-
Deprecated Interfaces
-
Deprecated ClassesClassDescriptionsince 2.0, the artifact types should be defined by the resolver consumerThis class is deprecated and is unused in Resolver. Use
PathProcessorSupportinstead.Hazelcast support will be dropped.Hazelcast support will be dropped.Hazelcast support will be dropped.Hazelcast support will be dropped.Hazelcast support will be dropped.definition and semantics of the scopes should be defined by consumer projectthe use of class should be avoided, seeStringDigestUtiland file processor in SPI modulefor removal. Nothing is using this class within Resolver.Do not use this class; is not used in Resolver (see corresponding processor components inorg.eclipse.aether.spi.iopackage).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.useConfigurableVersionSelectorinsteadsince 2.0, the DependencyTraverser implementation should be provided by the resolver consumerseePostorderDependencyNodeConsumerVisitorthat is more versatileseePreorderDependencyNodeConsumerVisitorthat 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, theScopeManagerexposed via methodRepositorySystemSession.getScopeManager()should be used.use snapshot filter instead to always ban snapshots
-
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.use @TempDir (JUnit 5) Or TemporaryFolder (JUnit 4) insteaduse@TempDir(JUnit 5) orTemporaryFolder(JUnit 4) insteaduse @TempDir (JUnit 5) Or TemporaryFolder (JUnit 4) insteaduseFiles.readAllBytes(Path)insteadUseMergeableMetadata.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 insteaduse SPI checksum selector insteaduse SPI FileProcessor to read and write checksum filesresolver 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.UseClassicDependencyManager(ScopeManager)instead to provide application-specific scope management. This constructor uses legacy system dependency scope handling which may not be appropriate for all use cases.UseDefaultDependencyManager(ScopeManager)instead to provide application-specific scope management. This constructor uses legacy system dependency scope handling.UseTransitiveDependencyManager(ScopeManager)instead to provide application-specific scope management. This constructor uses legacy system dependency scope handling.