Gradle
  1. Gradle
  2. GRADLE-1691

Tooling API should accept all the parameters not task name only

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: 1.0-milestone-3
    • Fix Version/s: 1.0-rc-2

      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.

        Activity

        Hide
        Kris De Volder added a comment - - edited

        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
        Show
        Kris De Volder added a comment - - edited 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
        Hide
        Kris De Volder added a comment -
        Show
        Kris De Volder added a comment - This issue is blocking https://issuetracker.springsource.com/browse/STS-1756
        Hide
        Davide Cavestro added a comment -

        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).

        Show
        Davide Cavestro added a comment - 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).
        Hide
        Kris De Volder added a comment -

        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.

        Show
        Kris De Volder added a comment - 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.
        Hide
        Szczepan Faber added a comment - - edited

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

        Show
        Szczepan Faber added a comment - - edited Not strictly related to the issue, but related to Kris' use case: GRADLE-1240
        Hide
        Szczepan Faber added a comment -

        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.

        Show
        Szczepan Faber added a comment - 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 .

          People

          • Assignee:
            Szczepan Faber
            Reporter:
            Greg Gigon
          • Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development