On 6 May 2013 19:16, Daz DeBoer <darrell.deb...@gradleware.com> wrote:
> On 3 May 2013 03:08, Peter Niederwieser <pnied...@gmail.com> wrote: > >> Devs, >> >> I've published a first version of the "custom Ivy status schemes" design >> spec here: >> >> https://github.com/gradle/gradle/blob/master/design-docs/custom-ivy-status.md >> >> If you are interested in reviewing the spec, please do so as soon as >> possible. My goal is to start on the implementation early next week. >> > > It looks like we are reinforcing 'status' and 'statusScheme' as a standard > piece of metadata that _all_ modules support. Is this what we want? How do > these concepts map to a maven repository, or a flatdir repository? > > Or should we be looking at introducing separate ivy/maven module apis, > like we have for publishing? > > Something like: > moduleMetadata.withType(IvyModule) { module -> > module.statusScheme = ['gold', 'silver', 'bronze'] > } > For now, I suppose we'd be creating a 'module' implementation for each unique combination of dependency and repository type. Haven't thought this through thoroughly, but trying to come up with a generic moduleMetadata api that maps to all repository types seems like it might be too much of a compromise. It would be great if eventually all of the code for handling ivy module resolution (including ivy repositories, 'latest.*' selectors, status schemes, etc) was in a separate 'ivy' plugin, not hard-wired into the core. >> Thanks >> Peter >> >> >> >> -- >> View this message in context: >> http://gradle.1045684.n5.nabble.com/Design-spec-custom-Ivy-status-schemes-is-ready-for-review-tp5711265.html >> Sent from the gradle-dev mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > > -- > Darrell (Daz) DeBoer > Principal Engineer, Gradleware > http://www.gradleware.com > Join us at the Gradle Summit 2013, June 13th and 14th in Santa Clara, CA: > http://www.gradlesummit.com > -- Darrell (Daz) DeBoer Principal Engineer, Gradleware http://www.gradleware.com Join us at the Gradle Summit 2013, June 13th and 14th in Santa Clara, CA: http://www.gradlesummit.com
