Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

./gradlew migrateToSplitties #222

Open
jmfayard opened this issue Oct 23, 2019 · 0 comments
Open

./gradlew migrateToSplitties #222

jmfayard opened this issue Oct 23, 2019 · 0 comments

Comments

@jmfayard
Copy link
Collaborator

jmfayard commented Oct 23, 2019

Not a blocker for now, but for the 3.0 release, we should expand the feature that was developed for ./gradlew migrateToAndroidX

## Your turn: add the AndroidX libraries to app/build.gradle

// app/build.gradle
dependencies {
    implementation(AndroidX.legacy.supportV4)
    implementation(AndroidX.legacy.supportV13)
    implementation(AndroidX.cardView)
    implementation(AndroidX.appCompat)
}

Code:

println()
println("## Your turn: use instead those Androidx libraries")
val map = artifacts.associate { it.supportArtifact to it.androidXArtifact }
val splitties = getArtifactNameToSplittiesConstantMapping()
println(gradleSyntax(androidSupportDependencies.mapNotNull { map[it.artifact] }, splitties))
}

What would need to change:

  • find a good name for the new task (hard)
  • have one task by project, instead of one task globally like migrateToAndroidX
  • consider all dependencies present in Splitties and not only AndroidX
  • use the right configuration name. Currently it's hacked together to use either implementation or androidTestImplementation.
@jmfayard jmfayard changed the title Mapping Splitties & Artifacts ./gradlew migrateToSplitties Oct 25, 2019
@jmfayard jmfayard mentioned this issue Oct 25, 2019
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant