Fix path based dependencies. See #282 and #253.

Detect dependency cycles after version resolution and before configuration resolution. Fixes #280.

Fix building sub packages that depend on their own parent package.

Fix usage of the selections file (was completely ignored) and improve diagnostic output.

Avoid internal exception when loading version selections.

Rename UpdateOptions->UpgradeOptions and move it to dub.dub.

Properly support path based version selections.

Fix validating the configuration graph. ...

getTopologicalPackageList(), which was used before, could yield a different set of packages.

Resolve sub packages of the root package directly instead of using the package manager. Fixes #287.

Fix null pointer dereference in Project.this() when no package was found. Fixes #286.

Fix compilation on DMD 2.064.

Fix path based dependencies to be ignored for version selections.

Implement user/system wide overriding of certain package version ranges. ...

What is still missing is a command line interface for conveniently setting the overrides.

Only validate (and output warnings) the root package once.

Improve the warning message for branch based dependencies.

Add a warning message for packages that use branch based dependencies.

Rename Project.mainPackage to rootPackage. ...

Root package better describes the package's role of the root of the dependency hierarchy.

Implement a new dependency resolution algorithm with support for selections. ...

The new algorithm is completely rewritten to be able to find any valid combination of dependencies/versions. The old one could error out in cases where a valid dependency tree could have been built. Now the current selections are also taken into account when invoking without UpdateOptions.upgrade.

Some side changes:
 - Comparing branch versions is allowed now to enable sorting the full set of versions of a package
 - DependencyGraph and RequestedDependency have been removed

Rename fields in Project and load the root package only once.

correct imports

Integrate the "dub select" functionality in "dub upgrade".

Make some cosmetic changes to dub version selections. ...

- Adjust code style
 - Let "dub select" output a simple package->version map instead of package->{version, dependencies}
 - Rename dub.select.json to dub.selections.json.

Preparing dub select command. dub select will select the currently used versions and write them to a file, so that dub can later use this information to rebuild this exact state. This will also be used to override dependencies with either branch versions or not matching versions (to resolve conflicts). (All of this if to be implemented). ...

Other changes:
- Added Version.UNKNOWN, which could be later used for undetermined package versions instead of ~master.
- Added Dependency to/fromJson.
- Added Dependency alias "*" for ">=0.0.0".

Not catching Throwable when metadata is fetched. ...

Documentation updated.

Add --force-remove switch and reimplement PackageManager.remove. ...

remove() now first checks for untracked files and leaves the package untouched if it finds some and no force_remove is supplied. This means that after the user gets an error concerning untracked files, it's possible to rerun dub with --force-remove to remove the package cleanly.

Avoid using the deprecated canFind function.

The externally defined sub-packages don't have the name declared in the base package. This eliminates the double definition of a sub-packages name.

Fix Project.getDefaultConfiguration to take the whole dependency tree into account.

Fix the configuration resolution algorithm. ...

The initial graph of the old algorithm contained edges to configurations that
couldn't themselves resolve all dependencies. These are now skipped, so that
only valid sub graphs exist. This avoids bogus "Could not resolve configuration
for package X" errors.

Keeping track of the saved json file in the journal and some smaller changes.