Initial GAX submission - generated classes only

[garrettjonesgoogle]

Also including updates from master.

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

[mziccard]

In the pom.xml do you mind replacing:

  <parent>
    <groupId>com.google.gcloud</groupId>
    <artifactId>gcloud-java-pom</artifactId>
    <version>0.0.7-SNAPSHOT</version>
  </parent>

with:

  <parent>
    <groupId>com.google.gcloud</groupId>
    <artifactId>gcloud-java-pom</artifactId>
    <version>0.0.11-SNAPSHOT</version>
  </parent>
  <properties>
    <site.installationModule>gcloud-java-gax</site.installationModule>
  </properties>

[garrettjonesgoogle]

Updated.

[aozarov]

I am not sure why the CLA verification is red. @jgeewax any idea?

Other than that looks good to me.

BTW, I think this approach of generating and including in the code common gRPC based classes (com.google.type.XXX) such as LatLng.java is going to get us into trouble at some point (e.g. datastore v1beta3 also includes them) as we will have the same classes (possiblly even with different
versions) multiple times in the class-path.

/cc @pcostell

[garrettjonesgoogle]

@wrwg, can you comment on the potential conflicts with common gRPC based classes, and what our longer term plan is for them?

[garrettjonesgoogle]

/cc @anthmgoogle

[anthmgoogle]

I'm seeing 3/6 commits not related to this change. The branch this is on may need rebasing.

[garrettjonesgoogle]

@anthmgoogle , those commits are there because of rebasing.

[wrwg]

@aozarov, we are building the grpc/proto generated libraries from the core up to form a clean hierarchy. The google/googleapis repo will go away, and will be replaced by a new repo which contains just the core protos, plus for each language a matching repo which can build and publish the generated artifacts.

For gcloud, we were suggesting to follow the same model. There will be a new repo gcloud-protos, and it would be submoduled by gcloud-java. The gcloud-java would reference an artifact for the java version of the generated files for the core platform, and can then build all the files you see in this PR (minus the ones in the core because they are packaged) from scratch.

There is a proof-of-concept (from which we are generating this PR), perhaps we can arrange for a showing.