Miłosz Lewandowski

Hi, thanks for reporting the issue! Could you please give some more details, does the analysis give wrong results for those libraries or an error/exception occurs?

Hi, both libraries are correctly reported when I add them to sample module in this repository: ``` Miloszs-MacBook-Pro:can-i-drop-jetifier miloszlewandowski$ git diff diff --git a/sample/build.gradle.kts b/sample/build.gradle.kts index 1eaff34..397209e 100644 --- a/sample/build.gradle.kts...

Hi, can you share some more details on why and how you use the dependency substitution - on which libraries, which versions etc.? Possibly create a clean project that reproduces...

Hi @stephanenicolas, thanks for reporting the issue! Indeed the problem could be resolving all configurations. I've just released a new version (0.3) that by default resolves only `*RuntimeClasspath` configurations, which...

OK. This indeed can be due to resolving configurations. Unfortunately, for now, I don't see a way to make the plugin work without resolving configurations due to the need of...

We also noticed this after bumping to 1.3.x. @ngsilverman could you please have a look at this?

Any update on this one? Apparently the code has been merged, but the plugin marker artifact never got published

@davidmotson sorry for mentioning directly, but I've seen that you are involved in a similar task for Firebase (https://github.com/firebase/firebase-android-sdk/issues/3125#issuecomment-966711911) which is going to be released soon, and you also contributed...

Is 3.43.0 published to Maven Central?

Is 3.45.0 published to Maven Central?