Contents
-
Deprecated Classes
Definition and semantics of the scopes should be defined by consumer project. Resolver out-of-the-box
supported scopes are defined in
DependencyScopes class. Resolver is oblivious about any other scopes and their
semantics.
The use of class should be avoided, see
StringDigestUtil and file processor in SPI module.
This class belongs to consumer project. Resolver have no notion of scopes other than those defined
in
DependencyScopes class, moreover it has no knowledge about scope transformation
of dependencies to build path scopes.
This class belongs to consumer project. Resolver have no notion of scopes other than those defined
in
DependencyScopes class, moreover it has no knowledge about scope transformation
of dependencies to build path scopes.
This class belongs to consumer project. Resolver have no notion of scopes other than those defined
in
DependencyScopes class, moreover it has no knowledge about scope transformation
of dependencies to build path scopes.
-
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.