Rename a build task to more clearly reflect what it builds

This task has an input named "hello_hash.ml", and an output named
"hello_hash.jar".  So calling this task "generateHelloHash" is too
vague.  Now we call it "generateHelloHashJar" instead.

com.ibm.wala.core.testdata/build.gradle

@@ -97,7 +97,7 @@ task unpackOcamlJava(type: Sync, dependsOn: downloadOcamlJava) {
 	into temporaryDir
 }
 
-task generateHelloHash(type: JavaExec, dependsOn: unpackOcamlJava) {
+task generateHelloHashJar(type: JavaExec, dependsOn: unpackOcamlJava) {
 	inputs.file 'ocaml/hello_hash.ml'
 	outputs.file 'hello_hash.jar'
 	args inputs.files.singleFile, '-o', outputs.files.singleFile
@@ -108,12 +108,12 @@ task generateHelloHash(type: JavaExec, dependsOn: unpackOcamlJava) {
 	inputs.dir ocamlJavaHome
 }
 
-task cleanGenerateHelloHash(type: Delete) {
-	delete generateHelloHash
+task cleanGenerateHelloHashJar(type: Delete) {
+	delete generateHelloHashJar
 	delete fileTree('ocaml') { exclude '*.ml' }
 }
 
-clean.dependsOn cleanGenerateHelloHash
+clean.dependsOn cleanGenerateHelloHashJar
 
 
 ////////////////////////////////////////////////////////////////////////
@@ -175,6 +175,6 @@ afterEclipseBuildshipImport {
 		collectTestDataA,
 		downloadJavaCup,
 		extractBcel,
-		generateHelloHash,
+		generateHelloHashJar,
 		)
 }

com.ibm.wala.core.tests/build.gradle

@@ -30,7 +30,7 @@ processTestResources {
 	from testdata.collectTestData
 	from testdata.downloadJavaCup
 	from files(testdata.extractBcel)[0]
-	from testdata.generateHelloHash
+	from testdata.generateHelloHashJar
 }
 
 test {