Hi guys, I started evaluating the new Transform API in Android Gradle Plugin 1.4.0-beta2, and I'm seeing a limitation which I wanted to consult with you about:
We at SafeDK are performing transformation on SDKs, as well as on the project's classes. For this we provide our Gradle plugin which developers need to use. Since SDKs could be anywhere (in the project lib, in source code, in external projects or external libs), we need to request a transform on all "scopes". Moreover, for other reasons, we need to output a single jar containing all SDKs. Therefore, as far as I could understand the new API, I need to use a CombinedTransform. However, using a CombinedTransform has quite a few downsides: 1. We will need to process jar files which normally we have no interest in (not all jars we consider as "SDKs") 2. We lose pre-dex capabilities, which would normally be done on all jars which are not SDKs. 3. Other plugins requesting transforms may request a limited scope, in which case they will fail. It would be great if there was an option in the API to return a list of jars and folders which are of interest to us, and the rest keep in the normal flow. Something like a "preTransform" method allowing us to evaluate the inputs and return a list of jars and folders which we are going to perform the transform on. Please let me know what you think, and whether there's a better way to achieve what I'm trying to do. Thanks! Ariel Cattan -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
