On 30 July 2013 17:23, Xavier Ducrohet <x...@google.com> wrote: > Makes sense. Right now I do want to add support for it so I'm going to use > the internal stuff. We are aware that this might mean we are only > compatible with a given version of Gradle and this is fine pre-1.0 > > I'm also going to start creating components for each variants, but only > add one candidate to the DefaultArtifactPublicationSet so this should work > by default like the old publication. >
Are you planning to publish multiple variants to the same GAV (publication), with variants differentiated by classifier? In that case, I'm not sure why you wouldn't just create a single component, with multiple artifacts. Each PublishArtifact can define a classifier, and all artifacts will be published. > > Quick question: what's the name of the Usage instances used for? > For Maven publication, it's not currently used. For ivy, it provides the configuration that contains the published artifacts. The mapping of SoftwareComponent/Usage => Maven/Ivy model is pretty brain-dead at the moment, and we'd be very willing to extend enhance this with more use cases. Daz
