On 09/11/2011, at 5:25 PM, Peter Niederwieser wrote: > > Szczepan Faber wrote: >> >> Interesting. Do you want to nominate other configuration to act as the >> 'default' or rather have the consumer explicitly declare it? Not sure if I >> understand it correctly :) >> > > I guess the idea is that a "compile" dependency on a project should, by > default, translate to something like that project's "archives" and "api" (or > "compile") configurations; a "runtime" dependency to that project's > "archives" and "runtime" configurations; etc.
Exactly right. There will be some convention that the publisher and consume agree on, and this convention will be baked into various plugins. We will define conventions for various types of projects, and people will be free to define their own. > Can't wait to have this. Me too. > > Cheers, > Peter > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/We-should-rename-the-default-configuration-tp4971272p4976861.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 > > -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
