[GRADLE-1395] gradle could reveal internal jars as a local repository Created: 22/Feb/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Spencer Allain Assignee: Unassigned
Resolution: Won't Fix Votes: 2


 Description   

gradle is essentially a local repository of very valuable jar files, but there is no easy convention to expose it as such. It would be great to say that I have a dependency upon jetty-6.1.25.jar or slf4j-api-1.6.1.jar and pull it out of gradle directly (when I want to of course - which is different from when things like that were unintentionally placed along the classpath).

Maybe like mavenCentral() there would be a gradleLocal() or gradleEmbedded() repository that would resolve artifact names according to the standard maven conventions.

 Comments   
Comment by Spencer Allain [ 07/Mar/11 ]

A workaround has been posted to the cookbook, and is listed below:

import org.gradle.api.internal.DefaultClassPathProvider
def classPathProvider = new DefaultClassPathProvider()
def File gradleHomeDir = classPathProvider.getGradleHome()

// NOTE: This will be null if gradle is not being loaded from a jar file
//       at which point a file resolver likely wouldn't work anyway
if (gradleHomeDir != null) {
  dirStr = gradleHomeDir.getCanonicalPath()
  repositories {
    flatDir name: 'gradleEmbedded',
            dirs: [dirStr + '/lib', dirStr + '/lib/plugins']
  }
}
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:54:28 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.