Wrapper around circular dependency strategy.
A component manager provides access to the pieces of xsbt that are distributed as components.
Represents an Ivy configuration.
Provides information about resolution of a single configuration.
Provide warnings for cross version conflicts.
Provide warnings for cross version conflicts. A library foo_2.10 and foo_2.11 can potentially be both included on the library dependency graph by mistake, but it won't be caught by eviction.
Configures how a module will be cross-versioned.
Rule to exclude unwanted dependencies pulled in transitively by a module.
sbt interface for an Ivy filesystem repository.
sbt interface for an Ivy filesystem repository. More convenient construction is done using Resolver.file.
Provides methods for working at the level of a single jar file with the default Ivy cache.
An enumeration defining the levels available for logging.
An enumeration defining the levels available for logging. A level includes all of the levels with id larger than its own id. For example, Warn (id=3) includes Error (id=4).
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.
Additional information about a project module
Provides information about the resolution of a module.
Provides information about the resolution of a module. This information is in the context of a specific configuration.
OrganizationArtifactReport represents an organization+name entry in Ivy resolution report.
OrganizationArtifactReport represents an organization+name entry in Ivy resolution report. In sbt's terminology, "module" consists of organization, name, and version. In Ivy's, "module" means just organization and name, and the one including version numbers are called revisions.
A sequence of OrganizationArtifactReport called details is newly added to ConfigurationReport, replacing evicted. (Note old evicted was just a seq of ModuleIDs). OrganizationArtifactReport groups the ModuleReport of both winners and evicted reports by their organization and name, which can be used to calculate detailed evction warning etc.
sbt interface to an Ivy repository based on patterns, which is most Ivy repositories.
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.
Basic SCM information for a project module
sbt interface for an Ivy repository over sftp.
sbt interface for an Ivy repository over sftp. More convenient construction is done using Resolver.sftp.
sbt interface for an Ivy ssh-based repository (ssh and sftp).
sbt interface for an Ivy ssh-based repository (ssh and sftp). Requires the Jsch library..
sbt interface for an Ivy repository over ssh.
sbt interface for an Ivy repository over ssh. More convenient construction is done using Resolver.ssh.
Represents unresolved dependency warning, which displays reconstructed dependency tree along with source position of each node.
Represents configurable options for update task.
Represents configurable options for update task. While UpdateConfiguration is passed into update at runtime, UpdateOption is intended to be used while setting up the Ivy object.
See also UpdateConfiguration in IvyActions.scala.
Provides information about dependency resolution.
Provides information about dependency resolution. It does not include information about evicted modules, only about the modules ultimately selected by the conflict manager. This means that for a given configuration, there should only be one revision for a given organization and module name.
sbt.RichUpdateReport
(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.
(Since version 0.13.6) HTTP repository is no longer recommended.
See http://ant.apache.org/ivy/history/latest-milestone/settings/conflict-managers.html for details of the different conflict managers.
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.6) HTTP repository is no longer recommended.
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.