I can't really say I agree that unit tests should only be run on the target
platform, although of course it does need to be tested on the platform. A
lot of unit tests are pretty darn useful for catching bugs outside of a
Dalvik environment. I often write Java code on one platform, say Windows,
and
How so? Aren't you running unit tests on the emulator?
On Sep 26, 2008 11:20 PM, "Shane Isbell" <[EMAIL PROTECTED]> wrote:
Nice, the only problem is that little things like unit tests no longer run.
Shane
On Fri, Sep 26, 2008 at 6:29 PM, Romain Guy <[EMAIL PROTECTED]> wrote: >
> Android.jar n
Fair enough. I'll just stub out my use of certain Android APIs so I can test
my code in a debugger.
Shane
On Sat, Sep 27, 2008 at 1:32 AM, Romain Guy <[EMAIL PROTECTED]> wrote:
>
> There is another big issue: there is absolutely NO guarantee that any
> of the classes from android.jar would run ou
Check this out
http://nader.shalabi.googlepages.com/androidapplications
On Thu, Sep 25, 2008 at 2:32 PM, friedger <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I used to have a look at the classes in android.jar using JadClipse.
>
> Since SDK 1.0 I only get class method looking like
>
> public void some
There is another big issue: there is absolutely NO guarantee that any
of the classes from android.jar would run outside of an Android
environment. They could rely on native libraries or special
initializations only provided by the full Android environment. Even if
a class runs now on top of Java S
Nice, the only problem is that little things like unit tests no longer run.
Shane
On Fri, Sep 26, 2008 at 6:29 PM, Romain Guy <[EMAIL PROTECTED]> wrote:
> Android.jar now contains only the public APIs. If you compile against this
> jar, you are guaranteed your app will run against future versions
Everything should, and now must, run on the emulator or on a device. This is
the only way to guarantee a program works (if only to run it on Dalvik
rather than a stock JVM.) For what it's worth, that's how we run all of our
tests in the Android team.
We have special support for tests, especia
On Sat, Sep 27, 2008 at 12:24 AM, Romain Guy <[EMAIL PROTECTED]> wrote:
> How so? Aren't you running unit tests on the emulator?
>
Some I do and some I don't. I've got the Masa plugins (for Maven builds)
setup to do both. By simply hooking a value object like ContentValues into
one of my classes,
Android.jar now contains only the public APIs. If you compile against this
jar, you are guaranteed your app will run against future versions of
Android. As part of the process that removes private APIs from android.jar,
the code is stubbed out, because it's never executed so there's no reason
> 2. How did you manage to do that? Code obfuscation is also an issue
> for us.
Note that the android.jar file size decreased from over 11 MB to under
3 MB (from SDK 0.9 to SDK 1.0). I also would like to know the code
optimizer / obfuscator that can do this :-)
Peli
PS: Ok, I assume that androi
Oh, yes, that "Stub!" thing :)
I hope this doesn't mean that there will be no source code release for
SDK... Otherwise, why "stubbize" android.jar?
BTW, decompilation is illegal, and is prohibited by license agreement.
On 25 сент, 18:32, friedger <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I used to ha
11 matches
Mail list logo
