Status Update
No update yet.
Comments
ad...@atlassian.com
this would be nice but given Compose and all other priorities, we are not planning to make any big investments in data binding (support KSP is a very big task).
sl...@google.com
be...@google.com
cm...@google.com
Makes sense. And is there any way to trigger data binding without kapt plugin, assuming there are no custom binding adapters in given module?
ad...@atlassian.com
unfortunately no. data binding still needs to be able to read your code and annotation processing is the only API that allows us to do it :(
cm...@google.com
It's a very disappointing decision for many projects who heavily depend on data binding, which will never be able to get rid of all bindings code and especially rewrite all UI to Compose.
It means that bindings are essentially deprecated
k....@gmail.com
It does not mean data binding is deprecated unless KAPT is deprecated (if that happens, we would need to support KSP).Unfortunately, moving data binding to KSP is a large order so it makes more sense to keep focusing on KAPT than rewrite data binding.
We might re-consider this in the future based on KSP becoming stable, Compose adoption and KAPT stability but it is very unlikely to happen.
sl...@google.com
nk...@google.com
Unfortunately this is still a NO for 2022 planning due to reasons mentioned in #2.
Description
Version used: espresso 3.0.1, runner:1.0.1
What steps will reproduce the problem?
1. Using this build.gradle from a standard library module created by the android studio 3.0.0 template
apply plugin: 'com.android.library'
android {
compileSdkVersion 26
defaultConfig {
minSdkVersion 16
targetSdkVersion 26
versionCode 1
versionName "1.0"
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
}
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
}
dependencies {
implementation fileTree(dir: 'libs', include: ['*.jar'])
implementation 'com.android.support:appcompat-v7:26.1.0'
implementation 'com.google.android.gms:play-services-auth:11.6.0'
testImplementation 'junit:junit:4.12'
androidTestImplementation 'com.android.support.test:runner:1.0.1'
androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.1'
}
2. execute ./gradlew :myLibrary:connectedAndroidTest
3. Results in
Execution failed for task ':mylibrary:transformResourcesWithMergeJavaResForDebugAndroidTest'.
More than one file was found with OS independent path 'protobuf.meta'
How are you running your tests (via Android Studio, Gradle, adb, etc.)?
run through Gradle.
What is the expected output? What do you see instead?
Expected successful build