Contents
-
Deprecated Classes
definition 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
for removal. Nothing is using this class within Resolver.
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.
since 2.0, the DependencyTraverser implementation should be provided by the resolver consumer
-
Deprecated Fields
use snapshot filter instead to always ban snapshots
-
Deprecated Methods
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.
-
Deprecated Constructors
Use
ClassicDependencyManager(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.