[GRADLE-1145] provide methods for major Maven repositories Created: 07/Sep/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9
Fix Version/s: None

Type: Improvement
Reporter: Dan Allen Assignee: Unassigned
Resolution: Won't Fix Votes: 2


It would be very helpful to have methods (or at the very least an alias map) for the major Maven repositories. Quite often builds depend on repositories in addition to Maven central, and having to remember those URLs taps the breaks on cranking out a quick build.

Here the repositories I propose, along w/ method name, alias and URL:

JBoss Community Public repository (composite of several different repositories, including glassfish, java.net, google code, codehaus)

Apache repository

SpringSource repository

Codehaus repository

JBoss Legacy repository <- not as important

Java.net repository

GlassFish repository

Comment by Dan Allen [ 07/Sep/10 ]

Obviously we have to draw the line somewhere on how many "standard" repositories to offer. My feeling is that between 5 and 10 is the right number...attempting to hit the majority of users needs.

Comment by Dan Allen [ 07/Sep/10 ]

The end result would be something like:

apply plugin: 'java'

repositories {

The more extensible approach would result in:

apply plugin: 'java'

repositories {
   mavenRepo 'central'
   mavenRepo 'codehaus'

The second syntax makes much more sense to me.

Comment by Hans Dockter [ 13/Sep/10 ]

I like that. I guess the repos definitions would be part of the maven plugin. We could even make this generic. The maven plugin looks for a property/xml/groovy file which defines the repos and out of that it provides the methods above. It could also provide a hook where other plugins could add 'standard' repos.

Comment by Luke Daley [ 02/Aug/13 ]

Not sure on this.

These are all vendor/technology repos. Seems like that's a fuzzy line to walk. I think our current strategy of only having shorthands for popular aggregate repositories that everyone can potentially contribute to makes sense.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:48:05 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.