On 31/07/2013, at 5:58 AM, Xavier Ducrohet <x...@google.com> wrote: > I'm looking at making sure the Android plugin works with the new publishing > plugin. > > SoftwareComponent doesn't associate any dependencies with the "component". > > SoftwareComponentInternal does through the Usage interface but both are > internal. Should I just start using those anyway? (I need that to publish > Android Libraries). > > What's the ETA for the feature to be stable and those API to move out of > internal?
Once we can publish multiple variants of an Android library :) The plan was to make these stable once we've solved a couple of major use cases. The first is to be able to publish and resolve a C++ component with multiple variants. The second is to formalise the lifecycle of a domain object to address things like laziness and mutability and so on, using the publication model to drive this. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
