[GRADLE-1691] Tooling API should accept all the parameters not task name only Created: 26/Jul/11  Updated: 04/Jan/13  Resolved: 15/May/12

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

Type: Improvement
Reporter: Greg Gigon Assignee: Szczepan Faber
Resolution: Fixed Votes: 3


 Description   

The tooling API used for embedding Gradle takes only the task name as a parameter. It should accept more parameters that are passed normally via command line, like build file, project parameters (-P) etc.

 Comments   
Comment by Kris De Volder [ 28/Oct/11 ]

Just trying to make a list of stuff (parameters) not yet explicitly mentioned in the description above that is also important:

  • Location of the Java install (or maybe is a special case of setting env params: JAVA_HOME)
  • Java options (location of Java distribution, heap, stack, permgen...)
  • system properties
  • os environment parameters
Comment by Kris De Volder [ 01/Nov/11 ]

This issue is blocking https://issuetracker.springsource.com/browse/STS-1756

Comment by Davide Cavestro [ 09/Nov/11 ]

Having the ability to specify certain params, such as --profile, would be very good to collect data that could really differ when obtained from CLI and from from IDE (through the tooling api).

Comment by Kris De Volder [ 17/Nov/11 ]

Another report of people having issues with JAVA_HOME env parameter for gradle tasks in STS:
https://issuetracker.springsource.com/browse/STS-2276

On the IDE side there is nothing that I can do about this since, it seems the IDE has no means to exert any control over what Java home will be used by the spawned daemon. This results in some people ending up unable to run compile related gradle tasks if they accidentally end up with a JRE being used.

Comment by Szczepan Faber [ 20/Nov/11 ]

Not strictly related to the issue, but related to Kris' use case: GRADLE-1240

Comment by Szczepan Faber [ 15/May/12 ]

This has been fixed in 1.0-rc-2. All build parameters are supported by the tooling API now. Certain command line options are not supported (for example --daemon), though. For more information please refer to: http://wiki.gradle.org/display/GRADLE/Gradle+1.0-rc-1+Release+Notes#Gradle1.0-rc-1ReleaseNotes-ToolingAPIallowsprovidingbuildargumentsforrunningtasksorbuildingmodel.

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