Skip to content

proguardInJars should not have all jars from the dependencyClassPath #19

@phdoerfler

Description

@phdoerfler

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions