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

dependencyReport does not notice updates to build.gradle

    Details

    • Type: Bug
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: 0.9
    • Fix Version/s: None

      Description

      Working on cleaning up my dependencies and found that the dependency report does not regenerate after a chance to build.gradle.

      gradle dependencyReport
      ... editing build.gradle and save
      gradle dependencyReport

      yields:
      :fissuresUtil:dependencyReport UP-TO-DATE

      BUILD SUCCESSFUL

      Seems like dependency report should declare that the build file in an input

        Activity

        Hide
        hans_d Hans Dockter added a comment -

        Did you change the dependencies section with your build.gradle update?

        Show
        hans_d Hans Dockter added a comment - Did you change the dependencies section with your build.gradle update?
        Hide
        mathias Mathias Kalb added a comment -

        I also had this problem with the version 0.9rc3

        Show
        mathias Mathias Kalb added a comment - I also had this problem with the version 0.9rc3
        Hide
        mathias Mathias Kalb added a comment -

        I tested it with version 0.9.1.

        If you change the dependency section (add, remove or change dependencies) the dependencyReport doesn't notice that.

        Show
        mathias Mathias Kalb added a comment - I tested it with version 0.9.1. If you change the dependency section (add, remove or change dependencies) the dependencyReport doesn't notice that.
        Hide
        bmuschko Benjamin Muschko added a comment -

        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!

        Show
        bmuschko Benjamin Muschko added a comment - 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!

          People

          • Assignee:
            Unassigned
            Reporter:
            crotwell Philip Crotwell
          • Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:

              Development