Closed GoogleCodeExporter closed 9 years ago
Original comment by chiragsh...@gmail.com
on 17 Sep 2012 at 12:33
This indeed should be a quick win! Maybe merge it with
https://github.com/evert/google-api-php-client
The big pros of this fork can be found in the Fork Information
https://github.com/evert/google-api-php-client#fork-information
Original comment by Rvanlaak
on 2 Nov 2012 at 2:49
There is sort-of Composer support via the Composer Classmap functionality:
http://getcomposer.org/doc/04-schema.md#classmap
I import the entire Google library by adding the following code in my
composer.json:
"autoload": {
"classmap": ["vendor/google-api-php-client/src/"]
}
So, adding it to Packagist and maintaining the tags should be the latest step
for now
Original comment by Rvanlaak
on 8 Nov 2012 at 1:31
Hi,
For convenience, please find attached a working example of a composer.json
file. If would be great if it could be included at the root of the source code.
Cheers,
Andrew
Original comment by andrew.z...@gmail.com
on 17 Jan 2013 at 1:00
Attachments:
It is also possible to define your own package in your project's composer.json
file:
{
"require": {
"google/google-api-php-client": "0.6.*"
},
"repositories": [
{
"type": "package",
"package": {
"name": "google/google-api-php-client",
"version": "0.6.0",
"dist": {
"url": "http://google-api-php-client.googlecode.com/files/google-api-php-client-0.6.0.tar.gz",
"type": "tar"
},
"autoload": {
"classmap": ["src/"]
}
}
}
]
}
Original comment by jorisvan...@gmail.com
on 18 Feb 2013 at 3:28
Thank you for the tip!
Original comment by andrew.z...@gmail.com
on 21 Feb 2013 at 10:19
Original comment by ianbar...@google.com
on 22 Mar 2013 at 3:31
Do you guys mind getting around to tags soon? I can't rely on trunk to
integrate this and we're heavy API users and customers.
Original comment by klimp...@gmail.com
on 2 Apr 2013 at 10:07
I added a tag for the last release, 0.6.1, and we'll keep adding tags as we cut
new releases.
Original comment by ianbar...@google.com
on 5 Apr 2013 at 3:15
What is the status of this?
Would it be possible to create a composer package any time soon?
Original comment by ales.sar...@gmail.com
on 4 Jun 2013 at 8:09
After @jorisvan's composer inclusion,
If have permission error like this "failed to open stream: Permission denied
in", just change your vendor's permission for www-data user.
It may help for someone like me.
Original comment by erheme...@gmail.com
on 11 Oct 2013 at 8:39
The permission issue is already open:
http://code.google.com/p/google-api-php-client/issues/detail?id=375
It's open for almost 3 months without any progress...
Original comment by ales.sar...@gmail.com
on 11 Oct 2013 at 9:35
What is the status on this? I'd love to help out in any way that I can. This
issue has been open for over a year now and in that time several other
non-official forks available on Packagist.
Original comment by simen...@gmail.com
on 12 Nov 2013 at 11:42
We've been working on the new version, it is currently available in Github and
there is a provisional package in Packagist:
https://packagist.org/packages/google/apiclient
- take a look, please let us know if you have any feedback, we are hoping to be
able to move to that version in the next couple of months.
Original comment by ianbar...@google.com
on 13 Nov 2013 at 4:33
This issue tracker is now closing. Development on the Google PHP client library
moved to GitHub with the release of the 1.0.0-alpha, and now the 1.0 branch has
reached beta status there will be no further releases of the 0.6 branch of the
library.
Please take a look at the latest version on
https://github.com/google/google-api-php-client
For information on migrating, please take a look at this guide:
https://developers.google.com/api-client-library/php/guide/migration
For general library support please ask a question on StackOverflow:
http://stackoverflow.com/questions/tagged/google-api-php-client
If you are looking for support with a specific API, please contact the team
working with that API via StackOverflow or their preferred support mechanism.
If your issue still exists with the new version of the library, please raise a
bug in the GitHub issue tracker with a minimal code sample.
Thanks!
Original comment by ianbar...@google.com
on 22 Jan 2014 at 4:53
Original issue reported on code.google.com by
klimp...@gmail.com
on 5 Sep 2012 at 2:03