Adam Murdoch wrote: > > 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. >
That would be good. Very nice way to provide a bootstrap for an open-source project with all sensible defaults. Another bootstrapping issue Maven has no easy solution for is directing all company builds to use a specific internal repo. I wonder what can be done with Gradle here. The scenario is : you have lots of projects and lots of developers in an organisation and you want all of them to use an internal repository and nothing else. This repo is Artifactory or Nexus, proxying all external repos. Its URL may change from time to time but when it happens - all builds start using the new URL right away. Today, we keep a company-specific "settings.xml" in all Maven installations to provide an Artifactory link, mirroring out everything (<mirrorOf>*</mirrorOf>). So you don't want to hardcode this URL in every Gradle build, but keeping it outside the build has other disadvantages, just mentioned. Seems to me this can be a plugin querying for a "company repo URL" over the internal network when the build starts, similarly to how IDEA checks its license. ----- 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-tp4739999p4742954.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
