title: Minimum impact proguard configuration on Android
body: <p>I have a simple problem: A third party dependency jar (BouncyCastle) that I want to shrink to avoid the 65k method dex limit.
  But using ProGuard creates thousands (literally!) of new problems (in addition to the warnings it generates): Explicit coupling between my third party libraries and proguard config files which to me seems ridiculous. But enough bashing of ProGuard...</p>
  
  <p><strong>Is there a way to tell ProGuard to exclude most of the code and only optimize/shrink/etc the one library that I have a problem with?</strong></p>