File	Date	Author	Commit
src	2011-01-10	nkeynes	[6ee154] Change isDexCurrent() to compare timestamps >= ...
.hgignore	2010-12-31	nkeynes	[b93677] Rearrange source tree to follow the maven defaults
.hgtags	2011-01-10	nkeynes	[b4519b] Added tag dedex_0_4 for changeset 6ee154d3ce42
.project	2010-11-29	nkeynes	[c041f6] Initial commit. Dex loading is largely working now
README	2011-01-03	nkeynes	[1b0b0b] Tweak command-line options, and printing of the...
dedex.sh	2010-12-24	nkeynes	[4da40a] Update copyright notices and source url
pom.xml	2010-12-31	nkeynes	[b93677] Rearrange source tree to follow the maven defaults

Read Me

Dedex 0.4 - a Dalvik-to-JVM converter.

Usage: 

java -jar dedex-0.4.jar [options] <input-dex-file>

Output options (at most one may be specified):
  -D, --dump                Disassemble dex file to console
  -d, --dir=DIR             Write class files to the given directory
  -o, --output=JAR-FILE     Write class files to the given .jar file

Other options:
  -c, --class=CLASS         Specify a single class to generate
  -h, --help                Print this help message
  -v, --verbose             Verbose disassembly (with -D)
  -V, --verify              Verify generated bytecode

  If no output options are given, dedex will create a .jar file in the current
  directory for each input .dex file.

Known Limitations:

  * Optimized dex files (ODEX) are not supported

  * Method body layout optimizations perform by dx are not reversed - this
     can confuse Jode, which currently makes assumptions about the code
     organization.

  * Generated JVM bytecode is not optimized in any way.