From b099564955aad95b9a43d198328732753a71ab38 Mon Sep 17 00:00:00 2001
From: Michael Bayne <mdb@samskivert.com>
Date: Fri, 14 Nov 2014 08:39:47 -0800
Subject: [PATCH] Bump Proguard versions.

Proguard 5.x finally supports Java 8. We don't compile Getdown to Java 8
bytecode, but Progaurd has to grok the stdlib of the JVM being used to run
Proguard, which previously meant that we couldn't compile Getdown with a Java 8
JVM, which was annoying. Now we can. Yay!
---
 pom.xml | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/pom.xml b/pom.xml
index 3db550f..208f75b 100644
--- a/pom.xml
+++ b/pom.xml
@@ -133,10 +133,9 @@
         </configuration>
       </plugin>
       <plugin>
-        <!-- TODO: return to stock groupId when they make it work with 4.5+: com.pyx4me -->
         <groupId>com.github.wvengen</groupId>
         <artifactId>proguard-maven-plugin</artifactId>
-        <version>2.0.6</version>
+        <version>2.0.8</version>
         <executions>
          <execution>
            <phase>package</phase>
@@ -147,12 +146,12 @@
           <dependency>
             <groupId>net.sf.proguard</groupId>
             <artifactId>proguard-base</artifactId>
-            <version>4.8</version>
+            <version>5.1</version>
             <scope>runtime</scope>
           </dependency>
         </dependencies>
         <configuration>
-          <proguardVersion>4.8</proguardVersion>
+          <proguardVersion>5.1</proguardVersion>
           <outputDirectory>${project.build.directory}</outputDirectory>
           <outjar>${project.build.finalName}.jar</outjar>
           <injar>${project.build.finalName}.jar</injar>