Use HTTPS instead of HTTP to resolve dependencies (#494)

This fixes a security vulnerability in this project where the `pom.xml`
files were configuring Maven to resolve dependencies over HTTP instead of
HTTPS.

Signed-off-by: Jonathan Leitschuh <Jonathan.Leitschuh@gmail.com>

pom.xml

@@ -205,7 +205,7 @@
             <id>central-repo</id>
             <name>Maven Repository</name>
             <!-- HTTPS is unavailable for Maven Central -->
-            <url>http://repo.maven.apache.org/maven2</url>
+            <url>https://repo.maven.apache.org/maven2</url>
             <releases>
                 <enabled>true</enabled>
             </releases>
@@ -238,7 +238,7 @@
         <repository>
             <id>clojars-repo</id>
             <name>Clojars Repository</name>
-            <url>http://clojars.org/repo</url>
+            <url>https://clojars.org/repo</url>
             <releases>
                 <enabled>true</enabled>
             </releases>

streams-contrib/streams-provider-google/google-gplus/pom.xml

@@ -40,7 +40,7 @@
         <repository>
             <id>typesafe</id>
             <name>typesafe</name>
-            <url>http://repo.typesafe.com/typesafe/repo</url>
+            <url>https://repo.typesafe.com/typesafe/repo</url>
         </repository>
     </repositories>
 

streams-contrib/streams-provider-youtube/pom.xml

@@ -38,7 +38,7 @@
     <repositories>
         <repository>
             <id>google-api-services</id>
-            <url>http://google-api-client-libraries.appspot.com/mavenrepo</url>
+            <url>https://google-api-client-libraries.appspot.com/mavenrepo</url>
         </repository>
     </repositories>