[GRADLE-435] Searching for jars to run Gradle Created: 05/Apr/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Russel Winder Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

Reporting an exchange on the email list:

2009/3/26 Russel Winder <russel.winder@concertant.com>
On Thu, 2009-03-26 at 08:22 -0700, Luk Morbee wrote:
> You are right.

OK.

> The only other way I can think of is that you write a bat-file around the
> gradle.bat that adds your personal jars to the classpath.

I don't use Windows so I don't have to suffer the bat file But yes
Gradle should do something similar to Groovy in checking a location for
jars to load at boot time.

It seems that the gradle Posix script is a small variation on
startGroovy. After control is passed to Java code, Groovy then loads
various jars using a configuration file, before finalizing the
classLoader used to run the Groovy code. This stage is clearly not
happening with Gradle as there is no conf file anywhere. So there is no
configurable set of directories searched for jars.

This is I think a weakness and I think there needs to be a proposal to
fix it.

I guess a JIRA is required.

 Comments   
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:30:03 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.