From c330362cf089509c0e81455bf34ad40717c47b66 Mon Sep 17 00:00:00 2001
From: Hans-Christoph Steiner <hans@eds.org>
Date: Tue, 16 Sep 2014 18:58:01 -0400
Subject: [PATCH] do not run proguard in `ant debug` builds, it breaks the
 tests

The whole ant build system was built around the assumption that proguard is
only run on the release builds.  Running proguard on the debug builds
breaks the test instrumentation, which does something like insert the emma
methods into each class.  In theory, this could be fixed, but I think its a
bad idea to heavily customize the ant build system since its basically
deprecated in favor of gradle.

Here's the proguard warning message:
 [proguard] Warning: can't find referenced class com.vladium.emma.rt.RT
---
 custom_rules.xml | 19 -------------------
 1 file changed, 19 deletions(-)
 delete mode 100644 custom_rules.xml

diff --git a/custom_rules.xml b/custom_rules.xml
deleted file mode 100644
index b4ec86047..000000000
--- a/custom_rules.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project name="custom_rules">
-
-  <target name="javadoc" description="Generate Javadocs">
-    <javadoc sourcepath="${source.dir}"
-             destdir="${out.dir}/javadoc"
-             packagenames="org.fdroid.*"
-             windowtitle="${ant.project.name}"
-             doctitle="${ant.project.name}" />
-  </target>
-
-  <target name="-debug-obfuscation-check">
-    <property name="proguard.enabled" value="true"/>
-
-    <!--To avoid "Multiple dex files define..."-->
-    <path id="out.dex.jar.input.ref" />
-  </target>
-
-</project>