History log of /dalvik/dx/src/com/android/dx/Version.java
Revision Date Author Comments
82e8334a1c1af6261b5e105868c20d2ab6b8a13b 22-Aug-2013 Yohann Roussel <yroussel@google.com> Increment dx version to 1.8

(cherry picked from commit 39bcbf75923303d209b7e6640590cd7f5eaaa65a)

Change-Id: Iaddb2020b75f2bbba2e2ebda3a4465a890e361ca
a346a60f5fcc8572ee67c79a596349604f696a39 21-Mar-2011 Dan Bornstein <danfuzz@android.com> Update version number.

Change-Id: Id000377c913927e56a7e9e1732ff24f52bc25970
ae5bf3dbf425adf20bf6d4ac1786639aa216aeb0 28-Oct-2010 Dan Bornstein <danfuzz@android.com> Up the version number.

Change-Id: Ibf1e0471d1991c0b9ef7df847b427a3aead6fd4d
ec022295682131fd8ebd4619343060fd3554319b 24-Jun-2010 Dan Bornstein <danfuzz@android.com> Updated the warning about old-style inner class metadata to reflect
the current understanding of the situation.

The change affects diagnostic output but doesn't change anything about
dex file production, per se. I also added a new test each for dx and
the vm, checking that the warning gets emitted and demonstrating the
effect (respectively).

Though it's a pretty minor change, I bumped up the version number of dx.

Added bonus: Wrapped a couple of too-long lines that I happened to notice.

Bug: 2171430
Change-Id: If6afa4ba88dca9b0e6d88603e0a5fc2e36358115
39c5899d0359c386815f5f72991a3a2573135dbd 10-Dec-2009 Dan Bornstein <danfuzz@android.com> Preflight cleanup of Ropper.java for style, whitespace, etc., before doing
some more drastic modifications. Also, bumped up the version number, rather
than making changes first and then forgetting that important detail.
72e93344b4d1ffc71e9c832ec23de0657e5b04a5 13-Nov-2009 Jean-Baptiste Queru <jbq@google.com> eclair snapshot
d24414a5d1780ce25179f3467b228f9a53863fb4 17-Apr-2009 Dan Bornstein <danfuzz@android.com> Fix issue #1794388.

In particular, when encountering a known-null being used as an array,
always emit an instruction that's compatible with the element type
expected/encountered in context. This will sometimes lead to
surprising instruction choices, such as "aget-byte" when the original
source used a boolean[], but in all of these cases the output is valid
and behaves correctly, where "correctly" in this case means (a)
passing verification, and (b) throwing a NullPointerException if ever
executed.

The test case (dx test #111) reflects unsurprising expectations and
so needs updating, which I will do in a follow-up to this patch.

I know this makes me an awful git user, but I fixed some comments and
whitespace while I was in the territory and *didn't* turn these into
separate commits.
99409883d9c4c0ffb49b070ce307bb33a9dfe9f1 19-Mar-2009 The Android Open Source Project <initial-contribution@android.com> auto import //branches/master/...@140412
f6c387128427e121477c1b32ad35cdcaa5101ba3 04-Mar-2009 The Android Open Source Project <initial-contribution@android.com> auto import from //depot/cupcake/@135843
f72d5de56a522ac3be03873bdde26f23a5eeeb3c 04-Mar-2009 The Android Open Source Project <initial-contribution@android.com> auto import from //depot/cupcake/@135843
446b11cd80658706d77d58996670b8eead3683a4 13-Feb-2009 The Android Open Source Project <initial-contribution@android.com> auto import from //branches/cupcake/...@131421
2ad60cfc28e14ee8f0bb038720836a4696c478ad 21-Oct-2008 The Android Open Source Project <initial-contribution@android.com> Initial Contribution