Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proguardInJars should not have all jars from the dependencyClassPath #19

Open
phdoerfler opened this issue Mar 1, 2012 · 0 comments
Open

Comments

@phdoerfler
Copy link

the proguardInJars task gets all jars from the dependency classpath which includes all managed and unmanaged dependencies in Compile (good) as well as all dependencies for other configs than compile (bad). E.g. the test config (which for example pulls in scalaz from specs) and all sbt plugins like sbteclipse.

IMHO proguardInJars should solely include managed and unmanaged dependencies in Compile and not on dependency-classpath so it does not include sbt plugins, test frameworks and other stuff you definitely don't want in your proguarded jar.

thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant