Open joharei opened 2 years ago
I have the following custom grouping rule:
androidx.navigation:navigation(-*) ^^^^^^^^.^^^^^^^^^^.^^^^^^^^^^
This used to override this built-in rule (which is now outdated btw. I'll submit a PR to remove it):
androidx.navigation:navigation-compose ^^^^^^^^. ^^^^^^^^^^^^^^^^^^
But in 0.40.2 the built-in rule has started taking precedence again.
My versions.properties file now contains this:
versions.properties
version.androidx.navigation-compose=2.5.0-rc01 ## unused version.androidx.navigation.navigation=2.5.0-rc01
I'm also not sure what determines my androidx.navigation version anymore, since that entry is now ## unused, and there are no other androidx.navigation entries in the file.
androidx.navigation
## unused
version.androidx.navigation.navigation=2.5.0-rc01
Submitted a PR to remove the navigation-compose rule: #550. This issue is still valid for similar cases in the future.
navigation-compose
🐛 Describe the bug
I have the following custom grouping rule:
This used to override this built-in rule (which is now outdated btw. I'll submit a PR to remove it):
But in 0.40.2 the built-in rule has started taking precedence again.
⚠️ Current behavior
My
versions.properties
file now contains this:I'm also not sure what determines my
androidx.navigation
version anymore, since that entry is now## unused
, and there are no otherandroidx.navigation
entries in the file.✅ Expected behavior