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.
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 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 constructor that provides consumer application specific predicate.
Use constructor that provides consumer application specific predicate.
Use constructor that provides consumer application specific predicate.