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

Gradle downloads changing modules every build when using an ivy DependencyResolver

    Details

    • Type: Bug
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Gradle Forums topic Reference:

      Description

      If you specify a repository using an Ivy DependencyResolver, and set the cacheChangingModules timeout to zero, then for a SNAPSHOT module, the descriptor file (ivy.xml/pom.xml) and artifact files will be re-downloaded on every build.

      eg: This will result in *-SNAPSHOT.pom/.jar being re-downloaded every build.

      configurations.all {
      resolutionStrategy.cacheChangingModulesFor 0, 'seconds'
      }
      repositories {
      add(new org.apache.ivy.plugins.resolver.URLResolver()) {
      name = "repo"
      addIvyPattern("http://localhost:$

      {server.port}/repo/[organization]/ivy-[module]-[revision].xml")
      addArtifactPattern("http://localhost:${server.port}

      /repo/[organization]/[module]-[revision].[ext]")
      changingMatcher = 'regexp'
      changingPattern = '.SNAPSHOT.'
      }
      }

        Activity

        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:
            forums Gradle Forums
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development