I actually have two related questions:
- Can predefined constants be expanded in the task declarations as
<injar file="${build}/myjar.jar" />? - How can I reuse the classpath definition in proguard? What I am trying to achieve is not to specify the whole set of required libraries. They are quite a lot and they are already included in ant’s classpath with specific id.
Thanks a lot.
Martin
Of course you can use Ant variables. However from my point of view it is easier to write all command-line options into the body of the proguard task:
For converting a defined Class path to a string that can be included into the proguard definition you can use the Ant task PathConvert. The first example on the linked page should be what you need.
Update: How to get the quotes around the path entries has been answered here: How to properly quote a path in an ant task?