We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The official web page https://developers.google.com/api-client-library/java/ still references the old version 1.25.0.
The latest official generated library for Drive API
<dependency> <groupId>com.google.apis</groupId> <artifactId>google-api-services-drive</artifactId> <version>v2-rev361-1.25.0</version> </dependency>
But, I am using version 1.28.0 I found in maven repo for some libs:
<dependency> <groupId>com.google.apis</groupId> <artifactId>google-api-services-drive</artifactId> <version>v2-rev20190501-1.28.0</version> </dependency>
What is the correct and official version of the generated libraries?
Or should we generate our own?
The text was updated successfully, but these errors were encountered:
Apologies, we are in the process of updating those docs to point to the real latest versions.
The source code for the newest versions exists https://github.com/googleapis/google-api-java-client-services
Sorry, something went wrong.
I can't find the sources for Admin Directory API, they exist in a private repo?
The missing Admin APIs from the list was fixed in googleapis/google-api-java-client-services#2607. Links from the README to the list of services is being fixed in #1353
chingor13
Successfully merging a pull request may close this issue.
The official web page https://developers.google.com/api-client-library/java/ still references the old version 1.25.0.
The latest official generated library for Drive API
But, I am using version 1.28.0 I found in maven repo for some libs:
What is the correct and official version of the generated libraries?
Or should we generate our own?
The text was updated successfully, but these errors were encountered: