Uploaded image for project: 'Gradle'
  1. Gradle
  2. GRADLE-1765

Gradle Tooling API not obeying Gradle Wrapper settings for subprojects

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0-milestone-7

      Description

      When the Gradle Tooling API is invoked directly via a subproject it doesn't obey the gradle wrapper version from the parent project.

      I discovered this while experimenting with http://static.springsource.org/spring-security/site/source.html

      This project seems to the same bug as spring-integration: http://issues.gradle.org/browse/GRADLE-1701

      However, its gradle wrapper specifies to use M3 (which means that it should not hit the bug).

      It indeed does not hit the bug when the model gets built from the root project. However, when requesting a model build from one of the subprojects (such as will happen in STS if you perform a "refresh dependencies" operation on a specific subproject) then it seems to fall back to using the tooling api's default version rather than the wrapper default. In this case it will hit the bug (and the error message indicates M4 was being used).

      In my mind this is a rather serious bug because it causes very unpredictable behavior for multi-project builds in the IDE, where it somewhat randomly varies which gradle version you end up using depending on things such as project build order etc.

        Activity

        kdvolder Kris De Volder created issue -
        adammurdoch Adam Murdoch made changes -
        Field Original Value New Value
        Fix Version/s 1.0-rc-1 [ 10062 ]
        adammurdoch Adam Murdoch made changes -
        Fix Version/s 1.0-milestone-7 [ 10164 ]
        Fix Version/s 1.0-rc-1 [ 10062 ]
        tracker_integration Pivotal Tracker Integration made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        tracker_integration Pivotal Tracker Integration made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        tracker_integration Pivotal Tracker Integration made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        ldaley Luke Daley made changes -
        Workflow jira with pivotal tracker [ 14921 ] jira with pivotal tracker (no resolved, only closed) [ 17337 ]
        ldaley Luke Daley made changes -
        Workflow jira with pivotal tracker (no resolved, only closed) [ 17337 ] Copy of jira with pivotal tracker (no closed, only resolved) [ 19998 ]
        Status Closed [ 6 ] Resolved [ 5 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            kdvolder Kris De Volder
          • Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development