Daz DeBoer-2 wrote > 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?
Yes, that's the current thinking. In his code review, Adam proposed a few alternatives on how to deal with a "latest" version selector for Maven repositories. Daz DeBoer-2 wrote > 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. Making these Ivy-only features, rather than abstract concepts with a (potentially odd) mapping to Maven/flatDir, sounds attractive to me. However, without a way for users to associate a dependency with a repository (or repository type), I'm having a hard time to imagine how this could work. Would a "latest" version selector indicate that the dependency is only looked for in Ivy repositories? And if the version was changed to "1.0", the dependency would be looked for in all repositories? Sounds a bit scary. Cheers, Peter -- View this message in context: http://gradle.1045684.n5.nabble.com/Design-spec-custom-Ivy-status-schemes-is-ready-for-review-tp5711265p5711281.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
