I’m running dependency analysis on our project and...

# mvikotlin

[Zsolt.bertalan]

I’m running dependency analysis on our project and it wants me to split all MVIKotlin artifacts to Debug and Release declarations. I couldn’t find anything in the documentation about the debug artifacts. What are the differences? Should I do the split?

[Arkadii Ivanov]

I'm not 100% sure what you are doing. But I believe that debug/release is only applicable to Android. MVIKotlin is published in both variants for Android. Each variant should be selected automatically, depending on how you assemble your project - assembleDebug/assembleRelease.

[Zsolt.bertalan]

Dependency analysis is just a tool to highlight and correct unused/wrongly declared dependencies. A third of my report is about MVIKotlin, because it thinks that debug and release is specific in MVIKotlin, so I should declare them.
But if I understand it right, there is no functional difference between debug and release artifacts. In that case we don’t need the debug ones. Android projects can (and should, I think) use the release versions from third party libraries.
We need debug libraries for LeakCanary for example, just so the release version can be no-op. But here debug means different content, not the way you build the library.

[Arkadii Ivanov]

MVIKotlin is not different from any other android library in terms of debug/release publications. Currently both variants have the same functionality, but there is no guarantee that it will be like this in the future. In general, it should be ok to always use the release variant.

[Emanuel Moecklin]

@Arkadii Ivanov is there a reason to release the debug version at all (I can see the irony in that statement "release the debug version" 🙂)? I think from a library consumer perspective, the debug version isn't very interesting

[Arkadii Ivanov]

It is published by default by the maven-publish plugin. It is also the default behaviour when publishing an Android library. I believe it should be possible to always use the release variant when consuming the library.

[Arkadii Ivanov]

Ok, it seems that it's not "by default". I will consider publishing only release variants. Thanks.