On Mon, Mar 30, 2009 at 5:46 PM, BeWillDir <wmmichael...@gmail.com> wrote: > The dx command worked OK on the original system, but > not on the new one. Here's why: > > The proximate cause was that I was sloppy installing java. The new > (Debian) system has a java command that does this: > > b...@gizmo:~/android/Apprise$ java > Usage: gij [OPTION] ... CLASS [ARGS] ... > to invoke CLASS.main, or > gij -jar [OPTION] ... JARFILE [ARGS] ... > to execute a jar file > Try `gij --help' for more information. > > ...while the original system runs a Sun version. Changing a link in / > etc/alternatives fixed the problem. Of course, someone naive like me > likes to believe this shouldn't matter - dx should work in either > jre. OK, not naive. Idealistic.
Agreed, and since dx isn't doing anything particularly fancy, this perhaps indicative of a bug in gij. We've seen bugs in JREs creep up before, and there is even a bit of code in dx that detects one of the known failure modes, but yours is a new one (at least for me). I'd love to be able to detect it, so if you are so inclined, please try tracking down what the most immediate failure is. (That is, by the time it turns into a bogus constant pool index, it's probably too late, as that could have been a legitimate complaint.) If you can figure that out, then we can probably add another bit of detection code and maybe save some folks a little time down the line. Thanks for following up, and my apologies that I steered you in the wrong direction to begin with. -dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
