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!
This commit is contained in:
Michael Bayne
2014-11-14 08:39:47 -08:00
parent 00f0212673
commit b099564955
+3 -4
View File
@@ -133,10 +133,9 @@
</configuration> </configuration>
</plugin> </plugin>
<plugin> <plugin>
<!-- TODO: return to stock groupId when they make it work with 4.5+: com.pyx4me -->
<groupId>com.github.wvengen</groupId> <groupId>com.github.wvengen</groupId>
<artifactId>proguard-maven-plugin</artifactId> <artifactId>proguard-maven-plugin</artifactId>
<version>2.0.6</version> <version>2.0.8</version>
<executions> <executions>
<execution> <execution>
<phase>package</phase> <phase>package</phase>
@@ -147,12 +146,12 @@
<dependency> <dependency>
<groupId>net.sf.proguard</groupId> <groupId>net.sf.proguard</groupId>
<artifactId>proguard-base</artifactId> <artifactId>proguard-base</artifactId>
<version>4.8</version> <version>5.1</version>
<scope>runtime</scope> <scope>runtime</scope>
</dependency> </dependency>
</dependencies> </dependencies>
<configuration> <configuration>
<proguardVersion>4.8</proguardVersion> <proguardVersion>5.1</proguardVersion>
<outputDirectory>${project.build.directory}</outputDirectory> <outputDirectory>${project.build.directory}</outputDirectory>
<outjar>${project.build.finalName}.jar</outjar> <outjar>${project.build.finalName}.jar</outjar>
<injar>${project.build.finalName}.jar</injar> <injar>${project.build.finalName}.jar</injar>