[GRADLE-2718] NullPointerException in GUtil.addToCollection occurs when JavaExec args is NULL Created: 21/Mar/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.3, 1.4, 1.5-rc-3
Fix Version/s: None

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


We were trying to create a Gradle task to execute a Java class by taking in a System property.

task importDataRequest(type: JavaExec) {
main = 'com.somepath.ImportDataRequest'
classpath = sourceSets.test.runtimeClasspath
args 'data.xls'
args System.properties.'Product'

{ false }

doFirst {
if (!System.properties.'Product')

{ throw new GradleException("Please enter a product in following format '-DProduct=SOMETHING'") }


When we execute any task in the Gradle file, it throws up NullPointerException at GUtil.addToCollection(GUtil.java:138)

Caused by: java.lang.NullPointerException
at org.gradle.util.GUtil.addToCollection(GUtil.java:138)
at org.gradle.process.internal.JavaExecHandleBuilder.args(JavaExecHandleBuilder.java:179)
at org.gradle.api.tasks.JavaExec.args(JavaExec.java:262)
at build_44ksni8gkqcc3hjj640feu326k$_run_closure9.doCall(D:\project\AutoHubFull\AutoHub\EndToEndTests\build.gradle:134)
at org.gradle.api.internal.ClosureBackedAction.execute(ClosureBackedAction.java:58)
at org.gradle.util.ConfigureUtil.configure(ConfigureUtil.java:133)
at org.gradle.util.ConfigureUtil.configure(ConfigureUtil.java:113)
at org.gradle.api.internal.AbstractTask.configure(AbstractTask.java:425)
at org.gradle.api.internal.project.AbstractProject.task(AbstractProject.java:921)
at org.gradle.api.internal.BeanDynamicObject$MetaClassAdapter.invokeMethod(BeanDynamicObject.java:216)
at org.gradle.api.internal.BeanDynamicObject.invokeMethod(BeanDynamicObject.java:122)
at org.gradle.api.internal.CompositeDynamicObject.invokeMethod(CompositeDynamicObject.java:147)
at org.gradle.groovy.scripts.BasicScript.methodMissing(BasicScript.java:83)
at build_44ksni8gkqcc3hjj640feu326k.run(D:\project\AutoHubFull\AutoHub\EndToEndTests\build.gradle:129)
at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:52)
... 30 more

We found a workaround for this issue. Instead of just passing the property to arguments, we passed an empty string if NULL.
args (System. properties . 'Product' ? System. properties . 'Product' : '' )

We were able to get around this bug by adding the above line. We think it should be handled in Gradle.

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