How to load a lib with composer?

may help you . There's a bug in the composer.json for PHPGoogleMaps package. Directory structure after the installation doesn't follow PSR-0 autoloading standard.
I submitted a PR fixing the problem but until it's fixed you can define your own repository for the package (changing the target-dir):

{
    "require" : {
        "nategood/httpful":"*",
        "nesbot/carbon": "dev-master",
        "jakzal/php-google-maps": "dev-master"
    },
    "repositories": [
        {
            "type": "package",
            "package": {
                "name": "jakzal/php-google-maps",
                "version": "dev-master",
                "source": {
                    "url": "https://github.com/galen/PHPGoogleMaps",
                    "type": "git",
                    "reference": "master"
                },
                "autoload": {
                    "psr-0": {"PHPGoogleMaps": ""}
                },
                "target-dir": "PHPGoogleMaps"
            }
        }
    ]
}

hop of those help? Files
If you want to require certain files explicitly on every request then you can use the 'files' autoloading mechanism. This is useful if your package includes PHP functions that cannot be autoloaded by PHP.

{
   "autoload": {
       "files": ["src/MyLibrary/functions.php"]
    }
}

wish help you to fix your issue The reason is that multiple autoloaders might be present concurrently in one process if for example you run phpunit installed via composer, then your test bootstrap file will also include your project class loader, and so if we did a simple require it would redefine the ClassLoader class and do a fatal error. Using require_once would not work either since the ClassLoader.php file is present twice (one in PHPUnit, one in the project) with different paths. PHP would still include each of these once, leading in class redefinition.
This could be fixed with a simple if (!class_exists()) {} around the require, but unfortunately that kind of conditional class definition messes up APC on high traffic sites so we had to resort to this strange temporary autoloader hack to make it work everywhere.

I wish did fix the issue. .lock information is absolutely pinned, typically created by a composer update request based on the json information... but developers don't necessarily want to pin everything to an exact version, and without that .json file they have to upgrade the .lock file manually for every version upgrade of their dependencies.
The .lock also holds dependencies of dependencies, and dependencies of dependencies of dependencies, etc... whereas the .json file only holds immediate dependencies.... and as a developer, you should only need to control your immediate dependencies, and allow those libraries to control their own dependencies via their own .json files

Any of those help I was following the developer guide they have on the composer website and I encountered this error while trying to deploy the business network definition to the fabric.I'm using: , The problem was solved by uninstalling and reinstalling docker