Sam Edwards

Thanks for reporting this! `0.4.x` has been a struggle to get a really solid configuration-cache compatible experience. I'm sorry you are running into this, but glad `0.3.x` is working for...

Implementation Callout: File paths don't always match Gradle Paths, so a `.replace("/", ":")` isn't smart enough to handle those cases. Example: https://stackoverflow.com/a/19303545 ``` include ":logger" project(":logger").projectDir = file("../the-logger-module-folder") ```

Brilliant! Merging! Thank you!

@qwert2603 - Sorry, `dependency-guard` has been working for our use cases so I haven't had any extra time to look into this. Configuration Cache is important, but the workaround ensures...

Finally hitting this issue now that we're bringing in the compose-bom. From a technical standpoint, I'm not sure how to approach it quite yet. This is our code used to...

A workaround could be to add ``` baselineMap = { if (it.contains("-bom") { null } else { it } } ``` Returning `null` from the `baselineMap` lambda will remove it...

@ZacSweers - @devpalacio and I have been adding Version Catalogs on our projects here and see the same behavior. Because these show up in the `./gradlew :module:dependencies` list, this seems...

If this is added, do we have it behind a flag, or make it default behavior?

I wanted to call it baseline because like Android lint or dependency-guard, I'd want to see in source control that my baseline changed. This is because it's so easy to...

Yes, and for ordering/priority.