I'd probably proguard it and package it in the sam...
# announcements
a
I'd probably proguard it and package it in the same jar
l
You better let library consumers proguard themselves (you can still recommen it), unless you need to use Proguard for obfuscation purposes for a closed source library (but do not use it to optimize the dependencies like Kotlin stdlib).