Filter out invalid dependencies before starting the resolution process. ...

Package versions for which it is not possible to get an actual package description (e.g. due to non-existent paths or semantic errors in the package description) are now excluded from the dependency resolution process. Before this, they could erroneously be picked, resulting in an malformed dependency tree.

Fix purging of optional dependencies when sub packages are involved.

Fix test variable names.

Implement new optional dependency semantics. Fixes #361. ...

If no dub.selections.json file exists yet, optional dependencies will stay deselected by default, unless the "default" flag is set. If dub.selections.json exists, optional dependencies will only be used if present in that file, independently of their local installation state.

Add "default" flag to Dependency and fix "*" to match optional dependencies.

Extend DependencyResolver to properly handle optional dependencies.

Output hierarchical log messages during dependency collection.

Change internal logic error to assertion and improve error message. ...

After dependency resolution and Project.reinit(), *all* required dependencies should be present in m_dependencies.

Merge pull request #766 from D-Programming-Language/issue754-path-dependency-fail ...

Let dub.selections.json always have precedence. Fixes #754.

Merge pull request #738 from Yoplitein/cmakeBackslashes ...

CMake generator: always use forward slashes in paths

CMake generator: use forward slashes in paths on Windows

Add workaround for DMD 2.070.0 AA regression.

Properly handle path based selections for manual --root paths.

Parse the (undocumented) "version" field in dub.sdl.

Let dub.selections.json always have precedence. Fixes #754.

Merge pull request #528 from MartinNowak/fix528 ...

Fetch doesn't work for recently updated package

Make sublimetext generator create import paths for DKit

Typo in verify command line help

fix Issue #528 - fetch doesn't work for recently updated package ...

Revert "store metadata cache on disk"

This reverts commit 161aad0.

We only ask the package suppliers for metadata when upgrading or
searching a specific package version. In particular building an already
fetched package does not ask the package suppliers (only the package
manager responsible for locally installed packages).

In all cases where we get data from a package supplier we want to get
the latest available information. Therefor it doesn't make sense to
cache any metadata from the package suppliers on disk.

Not sure whether we still need the in memory metadata cache (e.g. for
multiple queries during dependency resolution).

Avoid possible range error.

Only use the first part of the Posix user info as name for "dub init". ...

On Linux, this is a comma separated list of fields, where the first field is the user's full name.

Fix class Dub's public default constructor.

Add "release-debug" default build type. See #747.

Fix interactive setting of package recipe format.

Add long-option for non-interactive init mode.

Centralize the logic to determine the latest available package version.

Implement interactive "init" command.

Let initPackage use the new recipe.io functionality and enable recipe customization.

Let Dependency.versionString output "~>" style version ranges.

Serialize "x:ddoxTool" for toSDL().