[GRADLE-1861] GUI silently ignores task arguments in invocatoin Created: 22/Oct/11  Updated: 16/Jan/17  Resolved: 16/Jan/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: None

Type: Bug
Reporter: Blaine Simpson Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

Behavior when "gradle --gui task1 task2" is run does not behave as the Gradle syntax message and the user guide describe:

USAGE: gradle [option...] [task...]

I think it would be more user friendly if "gradle --gui task1 task2" would start up the Gui and execute task1 and task2 either before, after, or instead-of, the default tasks task that it normally executes upon startup. I can understand if you think it better for "gradle --gui" to not accept task parameters, but it is just wrong to accept the task parameters without complaint or warning and ignore them. For a casual user running "gradle --gui aQuietTask", they can not tell that their quiet task has not in fact run.

Either gradle --gui should

  • Check for task arguments and produce an appropriate message that --gui and task names are mutually incompatible, and update the general syntax message line beginning with --gui to something like: 
    --gui    Launches A GUI application.  Tasks may not be specified with --gui.
  • Execute the specified tasks after rendering the Gui, either before or after the default tasks task runs
  • Execute the specified tasks after rendering the Gui, instead of the default tasks task.

 Comments   
Comment by Aaron J. Zirbes [ 26/Dec/12 ]

I'd prefer the option:

  • Execute the specified tasks after rendering the Gui, instead of the default tasks task.
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 Blaine Simpson [ 15/Nov/16 ]

Behavior like this is very non-intuitive and hence un-groovy.

Comment by Benjamin Muschko [ 16/Jan/17 ]

The Gradle GUI has been deprecated and is scheduled to be removed with Gradle 4.0. We are not going to work on this issue anymore.

Generated at Wed Jun 30 12:06:20 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.