A component manager provides access to the pieces of xsbt that are distributed as components.
Provides methods for working at the level of a single jar file with the default Ivy cache.
Represents a logical time point for dependency resolution.
Represents a logical time point for dependency resolution. This is used to cache dependencies across subproject resolution which may change over time.
A Resolver that uses a predefined mapping from module ids to in-memory descriptors.
A Resolver that uses a predefined mapping from module ids to in-memory descriptors. It does not handle artifacts.
Provides extra methods for filtering the contents of an UpdateReport
and for obtaining references to a selected subset of the underlying files.
Represents unresolved dependency warning, which displays reconstructed dependency tree along with source position of each node.
(Since version 0.13.8) We now use an Aether-based pom parser.
(Since version 0.13.0) Define a module using inline Scala (InlineConfiguration), a pom.xml (PomConfiguration), or an ivy.xml (IvyFileConfiguration).
(Since version 0.13.8) Use InlineConfigurationWithExcludes.
Configures logging during an 'update'.
Configures logging during an 'update'. level
determines the amount of other information logged.
Full
is the default and logs the most.
DownloadOnly
only logs what is downloaded.
Quiet
only displays errors.
Default
uses the current log level of update
task.
(Since version 0.13.8) We now use an Aether-based pom parser.
A component manager provides access to the pieces of xsbt that are distributed as components. There are two types of components. The first type is compiled subproject jars with their dependencies. The second type is a subproject distributed as a source jar so that it can be compiled against a specific version of Scala.
The component manager provides services to install and retrieve components to the local repository. This is used for compiled source jars so that the compilation need not be repeated for other projects on the same machine.