…h-38 without using metadata
* All configuration options available for repositories are now available for mirrors, so credentials, snapshot/update policies, etc. are all supported * Eliminates use of the mirror-matching syntax offered by DefaultMirrorSelector/mvn, in exchange for simpler repository name/url matching using either strings or regexes, as described in technomancy/leiningen#271.
Aether allows unmanaged dependencies to go through the CollectRequest by setting a property on the Artifact. This is similiar to the maven "system" scope. One use case is for tools.jar that ships with the jvm. Unfortunatly, this does make it easy to add dependencies that will not exist on other systems. It is implemented by using :file metadata on the coordinates to be consistent with other api methods.
Turns out aether only does mirroring internally for repos in transative dependencies. It is up to us to map the user supplied repos to mirrors.
…7abc3` in error messages, fixes gh-32
The current deploy/install functions do not expose all the functionality presented in Aether. Signatures cannot be sent, deploy requires jar and pom files, and install requires a jar file. This exposes a general api. It uses a tree-like map structure to allow install/deploys using Subartifacts. Subartifacts can have their own Subartifacts.
dependency-hierarchy would not return all the dependencies when passing it the same specs used to resolve-depenedncies if there was a snapshot or version range. Add within? method to do comparisions instead of select-keys or =.