Publish Proguard configs with Guava

[cpovirk]

We are working on some internally. Once they're ready, we should publish them in Guava. I don't know if there's a standard way to do this with Maven.

[JakeWharton]

Since Guava is dependency-free, you could publish a sibling artifact using the 'aar' packaging whose format allows embedding proguard rules.

Android users wanting the automatic rules would specify a dependency like

compile 'com.google.guava:guava:19.0@aar'

instead of just

compile 'com.google.guava:guava:19.0'

[JakeWharton]

(Dependency-free is important because using a package qualifier on a dependency skips the deployed pom.xml for looking up transitive dependencies)

[cpovirk]

Thanks. I take it that our <optional>true</optional> dependencies on various projects' annotation artifacts aren't a problem here?

[JakeWharton]

Right. Any build system parsing the pom.xml should ignore those anyway.

[breyed]

It would be great if there as a "it just works" solution. It all looks so good at first when a simple

compile 'com.google.guava:guava:19.0'

gives your project all the Guava goodness, but come time to build a real-world APK with

        minifyEnabled true
        shrinkResources true

the fun ends due to all the errors. The error messages are obtuse and don't even provide much clue that Guava's the cause.

[bryanstern]

Is this dead? The proguard rules in the wiki seem terribly out of date.

[kluever]

@netdpb any ideas?

[cpovirk]

We do have proguard.cfg files internally. We've just never published them :(

[bryanstern]

@cpovirk Any chance you could start including it in the public repo?