On 27/08/2011, at 8:21 PM, evgenyg wrote: > > Luke Daley-2 wrote: >> >> Even with that plugin I'm not sure it's a good idea. >> > > I see. Can you list the reasons? I'm not a big fan of Maven Central either > and run my own Artifactory repo. > The reason I thought it could make sense is that standard open-source > projects without requirements of additional repositories work only with > Central.
I think I'd rather have a plugin that says 'this is a standard open-source project', than to bake this into core. This plugin could do things such as: * add maven central as a repo (plus maybe some other 'standard' repos - java.net, spring, jboss, etc) * add source and javadoc jars * set up the publications and signatures for publishing to maven central * add tasks to build a distribution containing jars, docs and source. > > > ----- > Best regards, > > Evgeny > > evgeny-goldin.com > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Use-mavenCentral-as-a-default-repository-unless-specified-otherwise-tp4739999p4740969.html > Sent from the gradle-user 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
