Bug: 112104996
Change-Id: Ie2624c6441794dca713344a4120d8996a16e158d

Bug: 79597307
Change-Id: I1f20d5ca0e62522ef2dfb42dbcab75d489e0156a

Try and address the problem of using Proguard with applications that
duplicate some classes in android.jar, e.g. applications that
statically include junit.

See https://sourceforge.net/p/proguard/discussion/182455/thread/76430d9e/
for more information.

Rebuilt proguard with ant 1.10.1 and gradle 2.1

Bug: 30188076
Bug: 69156675
Test: make checkbuild
Change-Id: I574becf07ed4a247e966f2c023e4b95b5ffc4011

Bug: 30188076
Bug: 69156675
Test: make checkbuild

Change-Id: Id10148d6af7ce00376e420475471f23cbbf92b4b

Bug: 26555886
Change-Id: I9045628003e69b50bb50d71253729e7e525f57e3

am: a90d4116

* commit 'a90d4116':
  Rebuild proguard.jar with ant/gradle support.

am: b29a267e  -s ours

* commit 'b29a267e':
  Fix 'Exception in thread "main" java.lang.AbstractMethodError:'

By setting ANT_HOME and GRADLE_HOME in build/build.sh.

Bug: 26274804
Change-Id: Iad81e3f81759ebb3461bfedfc2fed0b0229acca8
(cherry-pick from commit eedc65a5)

When running with OpenJDK 8 (openjdk version "1.8.0_45-internal") on
module messaging, sometimes an odd exception is caught in main:
Exception in thread "main" java.lang.AbstractMethodError:
java.lang.Exception.getMessage()Ljava/lang/String;
at proguard.ProGuard.main(ProGuard.java:519)

It's not 100% reproducible. But it's certain to happen if you run the
same ProGuard tasks in parallel (e.g. x40).

The exception runtime type is actually
java.lang.ArrayIndexOutOfBoundsException, which I tracked down to
raise from MappingPrinter.visitLineNumberTableAttribute().
It's strange that the exception object is in a weird state that
e.printStatckTrace() throws java.lang.AbstractMethodError.
Other people have seen similar things too:
http://stackoverflow.com/questions/6777710/abstractmethoderror-on-calling-exception-printstacktrace

Using temparary variables low/high fixes the crash.
It seems to be an OpenJDK 8 bug.

Rebuilt the jar files by running build/build.sh.

Bug: 26274804
Change-Id: I773023b2dc57bd048c6781aded84e0c0df923a90
(cherry-pick from commit 9d99b19d)

By setting ANT_HOME and GRADLE_HOME in build/build.sh.

Bug: 26274804
Change-Id: Iad81e3f81759ebb3461bfedfc2fed0b0229acca8

When running with OpenJDK 8 (openjdk version "1.8.0_45-internal") on
module messaging, sometimes an odd exception is caught in main:
Exception in thread "main" java.lang.AbstractMethodError:
java.lang.Exception.getMessage()Ljava/lang/String;
at proguard.ProGuard.main(ProGuard.java:519)

It's not 100% reproducible. But it's certain to happen if you run the
same ProGuard tasks in parallel (e.g. x40).

The exception runtime type is actually
java.lang.ArrayIndexOutOfBoundsException, which I tracked down to
raise from MappingPrinter.visitLineNumberTableAttribute().
It's strange that the exception object is in a weird state that
e.printStatckTrace() throws java.lang.AbstractMethodError.
Other people have seen similar things too:
http://stackoverflow.com/questions/6777710/abstractmethoderror-on-calling-exception-printstacktrace

Using temparary variables low/high fixes the crash.
It seems to be an OpenJDK 8 bug.

Rebuilt the jar files by running build/build.sh.

Bug: 26274804
Change-Id: I773023b2dc57bd048c6781aded84e0c0df923a90

This will be used for automated notification of external vulnerability
reports.

Change-Id: I9aabbe75a1a06d0ec3421ac5e78c786a22e27325

* commit 'baa6a15c':
  Add MODULE_LICENSE file

Change-Id: Ia519f00065573092f0ef3e8ab8ce88258bd1ae86

* commit '6af8f100':
  Upgrade Proguard to 5.1.

Downloaded from:
http://sourceforge.net/projects/proguard/files/proguard/5.1/

Bug: 17550647

(cherry picked from commit 2270795f)

Change-Id: I4d4c6b4f11aca8d5595b7f285c675bc5873d5e24

Downloaded from:
http://sourceforge.net/projects/proguard/files/proguard/5.1/

Bug: 17550647
Change-Id: I2b4eab16eb7821fc232b294ab7f433aae08f71e1

* commit '3fd19dba':
  Increase the java heap to 512M when running proguard

All of us building on Macs are running out of java heapspace during the
proguard phase of the build. This CL fixes the problem.

Change-Id: I461bb14b2ff2491e43ef8e2312e76a2a8fc0ee24

Change-Id: I727039a1eb945a438432d5bab078379a27854c8f

Downloaded from:
http://sourceforge.net/projects/proguard/files/proguard/4.10/

Bug: 8992787

(cherry picked from commit b9cc48a4)

Change-Id: I6c619bc8b0493530470e134127a04c7143aeee2d

(Resurrecting 3082b4a5 which was lost in b9cc48a4)

Change-Id: I0868e7fbb944aa48a4ef29880fb0cc5faa51c2e7

Downloaded from:
http://sourceforge.net/projects/proguard/files/proguard/4.10/

Bug: 8992787
Change-Id: Ia07cc5b3feed443982b7e8f2a1f361479e735b18

So it supports Android Bugreport Syntax

Change-Id: I09713b53364a2e4cda44ee67325f183a54075433

building the Utopia jar file.

Change-Id: Id3491f1f8f1640aa532c5ec30353d26a8d7ff8ac

This reverts commit cfead780.
Bug: 6079915

Change-Id: Ie185d0be411a80cc6a330cafa8547252a7dc1d9c

You can find the changelog here
http://proguard.sourceforge.net/#downloads.html

* commit 'd889ce6d':
  Fix proguard wrappers.

Shell version: This fixes the simple case of
the proguard binary path having a space in it.

Bat version: Use %* to capture all arguments, not
just the first 9 ones. It's typical to have > 10.

Change-Id: I32e7bcbe0c78f7518a1d727e4d80c07ec6d673b5

Change-Id: I7ebb33bf0dcbde7186dc96020f5871dc14fad5d7

Change-Id: I5e7a3a7161faf357d09d34b3dba61c52be7ace07

Merge commit '198fe95b' into eclair-plus-aosp

* commit '198fe95b':
  android-2.1_r1 snapshot