When a full 'composer' cannot be constructed (because there is no
local composer.json and no global composer.json), some commands
(e.g. `show -a`) fall back to the default repositories from the
`$COMPOSER_HOME/config.json` file. Without this fix, any auth
configuration from `$COMPOSER_HOME/auth.json` is not used for
these repositories in such a fallback scenario.
Steps to reproduce:
* Configure a password-protected composer repository in
`$COMPOSER_HOME/config.json`.
* Configure valid credentials for that repository in
`$COMPOSER_HOME/auth.json`.
* Make sure there is no file `$COMPOSER_HOME/composer.json`.
* Ensure the current working directory has no `composer.json`.
* Run `composer show -a some/package`.
Expected: Information about `some/package` is shown without
needing to enter credentials.
Actual: A prompt "Authentication required" is shown for the
private repository. When running the same command in a dir
that has a `composer.json`, or when `$COMPOSER_HOME/composer.json`
exists, things work as expected.
Add 'git-bitbucket' and 'hg-bitbucket' in RepositoryFactory help to call good driver in vcs
Cause if you config your repository type with 'git'. the GitDriver is instantiate and not GitBitbucketDriver
Fix#5389
Arnout Boks
Jean Baptiste Noblot
Martin Hasoň
Christophe Coevoet
bohwaz
Jordi Boggiano
Niels Keurentjes