Example of adding the Google Cloud Storage NIO Provider to a legacy jar

This project shows how to add Google Cloud Storage capabilities to a jar file for a Java 7 application that uses Java NIO without the need to recompile.

Note that whenever possible, you instead want to recompile the app and use the normal dependency mechanism to add a dependency to gcloud-java-nio. You can see examples of this in the gcloud-java-examples project.

To run this example:

1. Before running the example, go to the Google Developers Console to ensure that Google Cloud Storage API is enabled.

2. Log in using gcloud SDK (gcloud auth login in command line)

3. Compile the JAR with:

   mvn package -DskipTests -Dmaven.javadoc.skip=true  -Dmaven.source.skip=true
   

4. Run the sample with:

```
java -cp gcloud-java-contrib/gcloud-java-nio/target/gcloud-java-nio-0.2.7-SNAPSHOT-shaded.jar:gcloud-java-contrib/gcloud-java-nio-examples/target/gcloud-java-nio-examples-0.2.7-SNAPSHOT.jar com.google.cloud.nio.examples.ListFilesystems
```

Notice that it lists Google Cloud Storage, which it wouldn't if you ran it without the NIO jar:
```
java -cp gcloud-java-contrib/gcloud-java-nio-examples/target/gcloud-java-nio-examples-0.2.7-SNAPSHOT.jar com.google.cloud.nio.examples.ListFilesystems
```

The sample doesn't have anything about Google Cloud Storage in it. It gets that ability from the NIO jar that we're adding to the classpath. You can use the NIO "fat shaded" jar for this purpose as it also includes the dependencies for gcloud-java-nio. The underlying mechanism is Java's standard ServiceLoader facility, the standard way to plug in NIO providers like this one.

If you have access to a project's source code you can also simply add gcloud-java-nio as a dependency and let Maven pull in the required dependencies (this is what the NIO unit tests do). This approach is preferable as the fat jar approach may waste memory on multiple copies of dependencies.