On Nov 21, 2010, at 3:30 PM, Adam Murdoch wrote:
> The Jar task has an archivePath property, so you can do something like
> 'project.jar.archivePath' to get the value. It can potentially be a bit
> tricky to get the timing right from inside a plugin, given, as you say, the
> value can be changed from its default value, right up until the jar is
> created. Can you give a bit more detail about what you need to do with the
> JAR file?
In the gradle-android-plugin I use the ProGuard tool to shrink the application
JAR file to the minimum by stripping out classes and other resources that are
not actually referenced by application code. In the first iterations I
configured ProGuard to use the build/classes directory as input, but for
various reasons it would work better for ProGuard to take the assembled JAR
file as input instead, so that is why I am interested in this information.
As for timing, the plugin positions the proguard task in between the jar task
and assemble task of the Gradle build lifecycle.
Does that help?
--
Jason Voegele
It is not doing the thing we like to do, but liking the thing we have to do,
that makes life blessed.
-- Goethe
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
