Fix configuration file lookup order.

Also search for DUB settings file in ../etc/dub/. Fixes #895. ...

The search happens relative to the executable file. This also contains two small refactorings to prepare for a separation of configuration files and cache files, which currently reside in the same folder.

Aggregate special directories in a single struct.

Encapsulate configuration data in a class.

Merge pull request #878 from dlang/restrict-recipe-comments ...

Enforce that recipe comments are the first thing in the source file.

Enforce that recipe comments are the first thing in the source file. ...

Apart from the optional shebang line...

Don't search the default source directories for sources for single-file packages. ...

Also disallows specifying source files or paths in the embedded package recipe.

Pass app arguments to ddox for "dub --build=ddox". ...

These will now be passed to "ddox generate-html" or "ddox serve-html" respectively in addition to the basic arguments supplied by dub.

Implement single-file package semantics. ...

Can be invoked by either running with the --single switch, or by omitting the command and instead specifying a file with a .d extension.

Avoid querying the registry for unregistered root packages.

Remove deprecated functionality to prepare for 1.0.0.

Deprecate dub.compilers.compiler.defaultCompiler and improve docs. ...

Merges the code from compiler.defaultCompiler into the Dub class.

Improves documentation comment for Dub.defaultCompiler.

Move compiler registration code from to dub.dub. ...

Breaks the import cycle between dub.compilers.compiler and dub.compilers.ldc/gdc/dmd.

Avoid some uses of deprecated property Package.dependencies.

Mention version of removal for all deprecated public symbols.

Fix behavior of "--data-list --data-0" and improve the Dub/Project.listBuildSettings API. ...

Uses an explicit enum instead of hidden boolean logic to determine the output format. This also fixes an segfault that was caused by the deprecated wrapper around the new API.

Make defaultPlacementLocation a member of Dub instead of a global.

Review and document dub.project. ...

Also lowers "--(string-)import-paths" to "--data=x --data-list".

Review and document module dub.dub. ...

Moves the module name determination code to dub.internal.utils and makes DependencyVersionResolver private, as that will probably change considerably in the future (no deprecation path for this, because it's unlikely to be used outside out DUB).

Deprecates Dub.list(String)ImportPaths, as these functions are fundamentally flawed, because they are taking just a subset of the possible fields in GeneratorSettings. listProjectData is the designated successor.

Review and document dub.packagesupplier.

Avoid any of the newly deprecated symbols. ...

The only exception is the serialization code, which still iterates over deprecated fields, as well as Package.dependencies, which will be replaced in the next commit.

Avoid API breakage vs. 0.9.24.

Store path based selections relative to the root package.

Store path based dependencies in dub.selections.json. Fixes #772.

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.

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 workaround for DMD 2.070.0 AA regression.

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

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).

Fix class Dub's public default constructor.