[GRADLE-618] Make defaultTask method accept non string notations. Created: 04/Sep/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Hans Dockter Assignee: Unassigned
Resolution: Won't Fix Votes: 1


From the user-list:

Russel Winder wrote:
I find using strings as identifiers somewhat infelicitous – I like
having language level symbols so as to avoid spelling error issues.
Also for me, strings are data not control.

So as a specific single example, I don't like having to use strings for
task names, as in:

defaultTasks ( 'flob' , 'adob' )

However, whilst task names were string everywhere I just got into the
habit of:

def flob = 'flob'
def adob = 'adob'
. . . defaultTasks ( flob , adob )
But now that task names are not strings in some places whereas they are
in others, things are getting to a "point of pain".

task printHelloWorld <<

Unknown macro: { println ( 'Hello World.' ) }

defaultTasks ( 'printHelloWorld' )

Is annoying me because the name of the task is not the same sort of
language structure everywhere. Am I on my own here? Have I missed
something? Is there something to think about?

Probably. The defaultTasks() method should probably accept exactly the same things as parameters that Task.dependsOn() does. Then, you could do:

task hello ...

defaultTasks hello
defaultTasks 'hello'
defaultTasks [hello]
defaultTasks { tasks.findAll

{ it.name == 'hello' }



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