Update readmes for latest release. (GoogleCloudPlatform#99)

Author: jsuereth

README.md

@@ -1,14 +1,9 @@
 # Open-Telemetry Operations Exporters for Java
 
-[![Build Status][circleci-image]][circleci-url]
+[![Maven Central][maven-image]][maven-url]
 
 Provides OpenTelemetry Exporters for Google Cloud Operations. 
 
-[circleci-image]: https://circleci.com/gh/GoogleCloudPlatform/opentelemetry-operations-java.svg?style=shield 
-[circleci-url]: https://circleci.com/gh/GoogleCloudPlatform/opentelemetry-operations-java
-
-
-
 ## Building
 
 This project requires a mock server for Google Cloud APIs.  To build and test, do the following:
@@ -44,3 +39,8 @@ See [Tracing Readme](exporters/trace/README.md) for installation and usage instr
 *Note: This is an alpha-release.*
 
 See [Metrics Readme](exporters/metrics/README.md) for installation and usage instructions.
+
+
+
+[maven-image]: https://maven-badges.herokuapp.com/maven-central/com.google.cloud.opentelemetry/exporter-trace/badge.svg
+[maven-url]: https://maven-badges.herokuapp.com/maven-central/com.google.cloud.opentelemetry/exporter-trace

RELEASING.md

@@ -62,22 +62,12 @@ Before any push to the upstream repository you need to create a [personal access
 token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/).
 
 
-## Download the mock server
-
-- Run the `get_mock_server.sh` script, which downloads the [mock server
-  executable](https://github.com/googleinterns/cloud-operations-api-mock/releases),
-  and saves the path.
-
-    ```bash
-    $ source ./get_mock_server.sh
-    ```
-
 ## Release a Snapshot
 
 If you've followed the above steps, you can release snapshots for consumption using the following:
 
 ```bash
-$ ./gradlew snapshot -Dmock.server.path=$MOCKSERVER
+$ ./gradlew snapshot
 ```
 
 ## Releasing a Candidate
@@ -88,7 +78,7 @@ For example, to release the v0.14.0-RC1 candidate, do the following:
 
 ```bash
 # Create the Candidate.
-$ ./gradlew candidate -Prelease.version=0.14.0-RC1 -Dmock.server.path=$MOCKSERVER
+$ ./gradlew candidate -Prelease.version=0.14.0-RC1
 # Push the tag publically.
 $ git push origin v0.14.0-RC1
 ```
@@ -106,8 +96,8 @@ After following the above steps, you can release candidates from `main` or `v<ma
 For example, to release the v0.14.0 candidate, do the following:
 
 ```bash
-# Create the Candidate.
-$ ./gradlew candidate -Prelease.version=0.14.0 -Dmock.server.path=$MOCKSERVER
+# Create the Release.
+$ ./gradlew candidate -Prelease.version=0.14.0
 # Push the tag publically.
 $ git push origin v0.14.0
 ```

exporters/auto/README.md

@@ -1,5 +1,7 @@
 # Auto-Instrumentation for OpenTelemetry in Google Cloud
 
+[![Maven Central][maven-image]][maven-url]
+
 ## Setup
 
 To instrument metrics and traces using the `opentelemetry-javaagent`, `opentelemetry-operations-java-auto-<version>.jar` can be used to provide opentelemetry exporters.
@@ -9,3 +11,7 @@ java -javaagent:path/to/opentelemetry-javaagent-<version>-all.jar \
      -Dotel.exporter.jar=path/to/opentelemetry-operations-java-auto-<version>.jar \
      -jar myapp.jar
 ```
+
+
+[maven-image]: https://maven-badges.herokuapp.com/maven-central/com.google.cloud.opentelemetry/exporter-auto/badge.svg
+[maven-url]: https://maven-badges.herokuapp.com/maven-central/com.google.cloud.opentelemetry/exporter-auto

exporters/metrics/README.md

@@ -1,5 +1,7 @@
 # Metrics Exporter
 
+[![Maven Central][maven-image]][maven-url]
+
 *NOTE: Metrics are still Alpha in OpenTelemetry, and the API is not guaranteed to be stable across versions.*
 
 Opentelemetry Google Monitoring Metrics Exporter allows users to send collected metrics
@@ -73,3 +75,7 @@ IntervalMetricReader reader =
 | deadline      | ??? | ??? | The deadline limit on export calls to Cloud Monitoring API | 10 seconds |
 | metricDescriptorStrategy | ??? | ??? | How to adapt OpenTelemetry metric definition into google cloud. `ALWAYS_SEND` will try to create metric descriptors on every export.  `SEND_ONCE` will try to create metric descriptors once per Java instance/classloader. `NEVER_SEND` will rely on Cloud Monitoring's auto-generated MetricDescriptors from time series. | `SEND_ONCE` |
 
+
+
+[maven-image]: https://maven-badges.herokuapp.com/maven-central/com.google.cloud.opentelemetry/exporter-metrics/badge.svg
+[maven-url]: https://maven-badges.herokuapp.com/maven-central/com.google.cloud.opentelemetry/exporter-metrics

exporters/trace/README.md

@@ -1,7 +1,9 @@
 # Cloud Trace Exporter for OpenTelemetry
 
   OpenTelemetry Google Cloud Trace Exporter allows the user to send collected traces to Google Cloud. 
-  
+
+[![Maven Central][maven-image]][maven-url]
+
  [Google Cloud Trace](https://cloud.google.com/trace) is a distributed tracing backend system. It helps developers to gather timing data needed to troubleshoot latency problems in microservice & monolithic architectures. It manages both the collection and lookup of gathered trace data.
 
 ## Setup
@@ -27,7 +29,7 @@ config:
 <dependency>
   <groupId>com.google.cloud.opentelemetry</groupId>
   <artifactId>exporter-trace</artifactId>
-  <version>0.11.0</version>
+  <version>0.14.0</version>
 </dependency>
 ```
 
@@ -86,3 +88,7 @@ Java 8 or above is required for using this exporter.
   - For more information on OpenTelemetry, visit: https://opentelemetry.io/  
   - For more about OpenTelemetry Java, visit: https://github.com/open-telemetry/opentelemetry-java  
   - Learn more about Google Cloud Trace at https://cloud.google.com/trace
+
+
+[maven-image]: https://maven-badges.herokuapp.com/maven-central/com.google.cloud.opentelemetry/exporter-trace/badge.svg
+[maven-url]: https://maven-badges.herokuapp.com/maven-central/com.google.cloud.opentelemetry/exporter-trace