[GRADLE-3181] Gradle wrapper fails with NullPointer Exception Created: 14/Oct/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

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


 Description   

Hi,

gradlew fails on my TeamCity agent with the following error:

D:\TeamCity\buildAgent2\work\f143a7864defc8db>.\gradlew.bat tasks
Downloading [1]https://binaries.domain.local/artifac...

Exception in thread "main" java.lang.NullPointerException
at org.gradle.wrapper.Install.listDirs(Install.java:92)
at org.gradle.wrapper.Install.access$200(Install.java:26)
at org.gradle.wrapper.Install$1.call(Install.java:61)
at org.gradle.wrapper.Install$1.call(Install.java:44)
at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:65)
at org.gradle.wrapper.Install.createDist(Install.java:44)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:126)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:56)

Here's the gradle-wrapper.properties:

distributionBase=PROJECT
distributionPath=wrapper/dists
zipStoreBase=PROJECT
zipStorePath=wrapper/dists
distributionUrl=https\://binaries.domain.local/artifactory/external-libs/gradle/gradle/2.1/gradle-2.1-bin.zip

Gradle version is 2.1.
Any ideas what could be causing this? Thanks!
----------------------------------------------------------------------------------------
[1] https://binaries.domain.local/artifactory/external-libs/gradle/gradle/

 Comments   
Comment by Gradle Forums [ 14/Oct/14 ]

I had a look around the code and it looks like listing files of the directory into which you are trying to install the distribution returns null and the NullPointerExceptions occurs. This might happen when there is a failure in the native JDK code providing the list of files. I can see that you are on Windows. Is it possible that the user running the command doesn't have rights to list files in the distribution directory?

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