[GRADLE-2577] Not able to run gradle samples - proxy error Created: 29/Nov/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

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


 Description   

When I try to run the quick start sample with gradle , I get the below error. I have done the proxy configuration as per the gradle manual.

D:\gradle\gradle-1.2\samples\java\quickstart>gradle build
:compileJava
NEGOTIATE authentication error: Invalid name provided (Mechanism level: Could no
t load configuration file C:\WINDOWS\krb5.ini (The system cannot find the file s
pecified))

FAILURE: Build failed with an exception.

  • What went wrong:
    Could not resolve all dependencies for configuration ':compile'.
    > Could not resolve group:commons-collections, module:commons-collections, versi
    on:3.2.
    Required by:
    :quickstart:1.0
    > Could not HEAD 'http://repo1.maven.org/maven2/commons...
    ollections/3.2/commons-collections-3.2.pom'. Received status code 407 from serve
    r: Proxy Authentication Required
  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug
    option to get more log output.

BUILD FAILED

Further details regarding the issue are posted in the gradle forum link below
http://forums.gradle.org/gradle/topics/proxy_error-1r4f6

 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 12:25:42 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.