On 27/08/2011, at 1:41 AM, Peter Niederwieser wrote: > 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.
Even with that plugin I'm not sure it's a good idea. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
