[GRADLE-1181] Gradle GUI: running a task with -a does not work Created: 18/Oct/10  Updated: 16/Jan/17  Resolved: 16/Jan/17

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

Type: Bug
Reporter: Etienne Studer Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

In the Gradle GUI, when running a target using 'Execute Ignoring Dependencies', the execution fails since there seems to be a space missing between the task name and the -a option.



 Comments   
Comment by Adam Murdoch [ 19/Oct/10 ]

Do you have some more details? A stack trace? Gradle version? Does -a work from the command-line with the same build?

Comment by Etienne Studer [ 20/Oct/10 ]

It's how the command is executed. The space is missing between task name and -a.

beluga:demo etienne$ gr -v

------------------------------------------------------------
Gradle 0.9-20101019080116+0400
------------------------------------------------------------

Gradle build time: Tuesday, October 19, 2010 8:01:16 AM MSD
Groovy: 1.7.5
Ant: Apache Ant version 1.8.1 compiled on April 30 2010
Ivy: 2.2.0
JVM: 1.6.0_20 (Apple Inc. 16.3-b01-279)
OS: Mac OS X 10.6.4 x86_64

Executing command: ":build-a"

FAILURE: Could not determine which tasks to execute.

  • What went wrong:
    Task 'build-a' not found in root project 'demo'. Some candidates are: 'build'.
  • Try:
    Run gradle tasks to get a list of available tasks.

BUILD FAILED

Total time: 3.975 secs

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 [ 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 11:49:02 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.