1

Is there any way to treat the "scala-library" JAR as provided using SBT 0.13.7?

I'm using sbt-proguard to package my JAR, which is later loaded dynamically into an application that already has an appropriately versioned scala-library on the classpath.

Rich Henry
  • 1,837
  • 15
  • 25
  • I'm able to use sbt-assembly and [exclude the scala-library](https://github.com/sbt/sbt-assembly#excluding-scala-library-jars), but I'd like to use the other functionality that proguard provides at some point. – Rich Henry Mar 25 '15 at 13:56

1 Answers1

0

The sbt-proguard plugin defaults to swallowing the entire world. If you don't want to process everything with proguard (and include it in the resulting jar), then you will need to redefine the inputs. For example with something like this in your build.sbt:

ProguardKeys.inputs in Proguard <<= exportedProducts in Compile map { _.files }

Dr.Haribo
  • 1,778
  • 1
  • 31
  • 43