A default repository would add considerable overhead for those that don't need it, and would pose a big security risk. (This holds even if the default repository is only added if the build doesn't declare any repositories.) There are companies that went as far as patching Maven (!) to make absolutely sure that their builds will never hit Maven Central. We shouldn't make the same mistake.
There are plans for a mavenCentral plugin that has everything that's needed for publishing to Maven Central. For such a plugin, this default might make sense. -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Twitter: @pniederw evgenyg wrote: > > Hi, > > I was wondering whether Maven Central > > > > can be made the default repository? This way the minimal build file can be > as simple as > > > -- View this message in context: http://gradle.1045684.n5.nabble.com/Use-mavenCentral-as-a-default-repository-unless-specified-otherwise-tp4739999p4740091.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
