It took me about 5 minutes to use the Google Translate REST API from Javascript, NodeJS, WGET and Java via Sun's Jersey library, but I cannot find any working examples for the current version of the official Google Java Client (rev41), or how to configure it using Maven. I sat for an entire morning trying to work it out from the source code (and swearing a lot) to no avail. Working out the Maven stuff was easy enough but I cannot for the life of me work out how to use the Java API - a crazy situation as it took so little time using basic generic technology.
For reference - this is my Maven config:
<dependency>
<groupId>com.google.apis</groupId>
<artifactId>google-api-services-translate</artifactId>
<version>v2-rev41-1.20.0</version>
</dependency>
My bigger question to the lovely Google folk is - why is the Java library harder to implement than using straight REST? Surely the sole purpose of the Java library is to provide a wrapper that makes using Google Translate simpler, and there are only about 3 REST calls to wrap, how hard can it be? What exists now would appear to be the opposite: a number of web articles actually recommend using a thirdParty non-official Java library, or even Google's text-to-speech service (How to use Google Translate API in my Java application?). All of this suggests to me that this area needs some attention or should be thrown in the bin, it's not currently adding any value.