[GRADLE-726] Provide Access to Runtime Classloader Created: 04/Nov/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Robert Fischer Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

It'd be nice to enable an API like this:
cl = configurations.runtime.classLoader

See the conversation here:
http://old.nabble.com/Runtime-ClassLoader-Instead-of-Build-ClassLoader-to26157974.html

Since tasks are often implemented as calls into Java classes, it would be nice if those calls could use the runtime (post-dependency-resolution) classloader instead of the buildscript classloader. Or if they could at least have access to them.

My particular use-case is working on Cucumber (via JRuby) and Gradle. I couldn't refer to classes compiled or access in the normal dependency system, so I had to dump all those dependencies into the buildscript dependencies:
http://enfranchisedmind.com/blog/posts/jruby-cucumber-gradle/

This basically means that any code I would use at runtime would have to go into the buildscript dependencies, which is just wrong. On the other hand, if I could set the ContextClassLoader to the runtime configuration classloader, I would be set.

 Comments   
Comment by Robert Fischer [ 08/Dec/09 ]

I've implemented this as one of my Gradle plugins:

http://github.com/RobertFischer/gradle-plugins

Gradle core is welcome to hijack the code (it's CC0).

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