[GRADLE-746] Name collision on variables vs task name confusion Created: 18/Nov/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

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


This is probably a limitation of Groovy but I thought I would log it anyways.

The following dependency for the task 'gwtCompile' didn't fire although I could call it directly from the command line with no problems (i.e. gradle gwtCompile). 'war.dependsOn gwtCompile' will not work (it gets skipped) unless I give it its own unique name.

gwtCompile = files(fileTree(dir: "$gwtDir", includes: ['gwt-servlet.jar','gwt-user.jar']), "$libDir/gxt/2.0.4/gxt.jar")

dependencies {
	compile gwtCompile, springCompile, hibernateCompile

task gwtCompile(type: GwtCompileTask) {
	gwtBuildDir = mkdir(buildDir, 'gwt')
	module = 'flexnet.compliance.web.gwt.ComplianceApp'
	gwtClasspath = configurations.gwt.asPath
	sourcepath = 'src/main/java'
	compileClasspath = configurations.compile.asPath

war.dependsOn gwtCompile

Comment by Hans Dockter [ 22/Nov/09 ]

I would say the bug is that Gradle does not throws an exception.

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