Hi, I had a problem with atrium on gradle 5.0 it is related with dependency scopes probably because I had a similar problem with mockk also. Is it a known problem?

what kind of problem do you encounter? there are a number of problems concerning runtimeOnly dependencies in gradle and in the kotlin plugin. For instance, https://guides.gradle.org/migrating-from-maven/#bills_of_materials_boms where the behaviour was changed with gradle 5.0

yeah that should be it.

was the problem in atrium itself? Or in other words, did you find a bug?

I didn’t really looked it in detail. I was checking if everything would work with gradle 5. so I am not sure where the problem is.

OK, please open an issue on github if atrium needs a fix

yeah sure.