sbt.librarymanagement

Work around the inadequacy of Ivy's ArtifactTypeFilter (that it cannot reverse a filter)

Cross-versions a module using the result of prepending prefix and appending suffix to the binary version. For example, if prefix = "foo_" and suffix = "_bar" and the binary version is "2.10", the module is cross-versioned with "foo_2.10_bar".

A reference to Configuration.

Represents an Ivy configuration.

Provides information about resolution of a single configuration.

See http://ant.apache.org/ivy/history/latest-milestone/settings/conflict-managers.html for details of the different conflict managers.

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.

Cross-versions a module using the string value.

Configures how a module will be cross-versioned.

DependencyBuilders implements the implicits for % and %% DSL.

Library management API to resolve dependencies.

Interface for dependency resolution intended for engine authors.

Disables cross versioning for a module.

Configuration specific to an Ivy filesystem resolver.

sbt interface for an Ivy filesystem repository. More convenient construction is done using Resolver.file.

Similar to Binary except that if the binary version is 2.13 it uses 3 instead. For example, if prefix = "foo_" and suffix = "_bar" and the binary version is "2.13", the module is cross-versioned with "foo_3_bar".

Similar to Binary except that if the binary version is 3 (or if it is of the form 3.0.0-x) it uses 2.13 instead. For example, if prefix = "foo_" and suffix = "_bar" and the binary version is "3", the module is cross-versioned with "foo_2.13_bar".

Cross-versions a module with the result of prepending prefix and appending suffix to the full version. For example, if prefix = "foo_" and suffix = "_bar" and the full version is "2.12.1", the module is cross-versioned with "foo_2.12.1_bar".

Defines a rule to either:

• Exclude unwanted dependencies pulled in transitively by a module, or to

• Include and merge artifacts coming from the ModuleDescriptor if "dependencyArtifacts" are also provided.

The use case that is applied depends on the parameter name which it is passed to, but the filter has the same fields in both cases.

Represents a logical time point for dependency resolution. This is used to cache dependencies across subproject resolution which may change over time.

An instance of maven CACHE directory. You cannot treat a cache directory the same as a a remote repository because the metadata is different (see Aether ML discussion).

This is the internal implementation of actual Maven Repository (as opposed to a file cache).

An instance of a remote maven repository. Note: This will use Aether/Maven to resolve artifacts.

Decribes the representation of a module, including its dependencies and the version of Scala it uses, if any.

Additional information about a project 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. 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 eviction warning etc.

Cross-versions a module by stripping off -bin-suffix. This is intended for patch-version compatible alternative replacements.

sbt interface to an Ivy repository based on patterns, which is most Ivy repositories.