Repair Android tests

[henri-tremblay]

It might require to migrate to Gradle

[gitryder]

Can I try to do this?

[henri-tremblay]

@gitryder Of Course! Go for it! Normally if you launch with the -Pall profile, you will things falling over.

[gitryder]

I'm sorry, I'm new to contributing. I don't understand what you're saying.

What's -Pall profile?

[henri-tremblay]

when launching maven build: mvn verify -Pall. Otherwise the android module isn't compiled. The README.md should explain how to work with Android.

[NyorJa]

Can I check this also? Thanks.

[henri-tremblay]

All help is appreciated. Start by getting a working build. I can give move details afterwards. Some working example could be https://github.com/raphw/byte-buddy/tree/master/byte-buddy-android-test

[yogurtearl]

The gradle to maven migration fails with an NPE on this project. :/
File here: gradle/gradle#14974

[yogurtearl]

Thoughts on just moving tck-android to gradle as a first step?
would probably have to run it with ./mvnw install -Pall && cd tck-android && ./gradlew connectedAndroidTest

[yogurtearl]

Here is a basic gradle setup that let's you run the Android test. -> #82

If you change minSdk to 21 and run ./gradlew connectedAndroidTest the build will fail.
https://github.com/yogurtearl/objenesis/blob/b6ee12c618897150d34651d28b6de479c8dcad7d/tck-android/build.gradle.kts#L29

With error:

D8: com.android.tools.r8.a: MethodHandle.invoke and MethodHandle.invokeExact are only supported starting with Android O (--min-api 26)

[nach-o-man]

@henri-tremblay I couldn't see any failing tests. Is this issue up-to-date?
Also created #84 with instructions for windows user on how-to run android tck

[henri-tremblay]

@nach-o-man Yes. The tests are "passing". But if you read the log, you will see that it looks like the test is actually failing with some error code. So the current build probably just doesn' detect the failure.