Open sylwek845 opened 1 year ago
Hey @sylwek845 thanks for reporting this. Adding a bit of context for this behavior, this is due to the fact that Grazel tries to do incremental migration by default. We explain it here https://grab.github.io/Grazel/migration_criteria/#migration-criteria. The problem is that the check is not as exhaustive and we don't have good tooling yet to display statistics on what was migrated. For fixing this we need two this at least
grazel {}
in addition to default MigrationCriteria
. WORKSPACE
as well to let versionConflictPolicy = "pinned"
to work. Gradle and rules_jvm_external
does dependency resolution differently, the proper way to fix it is ensure Grazel generates pinned versions of all artifacts (including transitives) in the project. Then rules_jvm_external
won't throw dependency resolution conflicts. This is currently being done as part of rewrite here #45. Will target this for 0.5.0.
Problem 1. Not sure why this is happening but it seems like some of my modules getting the
Deleted test/test_fixtures_ui/BUILD.bazel
and I don;t see the migratedBUILD.bazel
filemy config
Problem 2.
When I enable
artifactPinning
I get dependency conflict ->but adding
overrideArtifactVersions.add("androidx.navigation:navigation-runtime:2.3.2")
doesn't work at all.and I do get the same