[GRADLE-392] Upload Gradle Jar to public Maven repository Created: 10/Feb/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Peter Niederwieser Assignee: Unassigned
Resolution: Won't Fix Votes: 8


 Description   

Upload the Gradle Jar to a public Maven repository, so that projects with a compile-time dependency on the Gradle Jar can easily pull it from there.

 Comments   
Comment by Peter Niederwieser [ 20/May/09 ]

Can you make this happen for 0.6?

Comment by Hans Dockter [ 21/May/09 ]

I will try to tackle this next week.

Comment by Russel Winder [ 18/Jul/09 ]

Sorry to hassle, but Gradle not being in the Maven repository is a Very Bad Thing (tm).

Comment by Axel Fontaine [ 10/Jul/13 ]

I couldn't agree more. This is such a simple thing to fix!

It would enable a number of things like building Gradle plugins with Maven, ...

Comment by Lukas Eder [ 28/Aug/13 ]

@Hans Dockter: "next week" seems to have been a way ago

After Axel Fontaine (maintainer of http://www.flywaydb.org), I really want to help you understand that this improvement would be very very valuable to a great many of your users and other users. This would, for instance, also simplify things for code generation with Gradle in jOOQ (http://www.jooq.org).

Here are some useful guidelines about how to do that with Sonatype's OSS services:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
So +100 from me!

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:28:57 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.