I've been struggling to understand how to publish the N apks that an android build produces. Well, at least the debug and the release apk. Why both? Because QA needs both to do their job on the app we're working on. There may be multiple apks if we make use of product flavors. In the meantime over the last 3 years, Gradle has changed the way they publish artifacts, and the Android Gradle plugin has evolved to a point where we're all using it now.
So, how does one publish the apks? I still see no documentation on it. The issue is that Android ADDS complexity to gradle by building >1 artifact per build, thus if you read only the Gradle doc, you are told it can only upload either jar or web components.But if you try to read the Android Gradle doc, it details only how to publish the AAR file(s). Just HOW does one publish apks (release and debug) and if one has product flavors, how does one publish them? I am using a Nexus artifact repository, but seem to be unable to find any consistent documentation for the current, modern way to do this. -- 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.
