[GRADLE-2128] Ivy resolver changingPattern is ignored if changingMatcher is not specified Created: 27/Feb/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 1

Attachments: File ChangingModuleTest.zip    

 Description   

I define ivy resolvers directly still since the gradle ivy DSL does not yet have the changing* properties for ivy resolvers. It seems that with gradle-1.0-milestone-8 gradle has stopped honoring the changingPattern though. For instance, if I define a local filesystem resolver like so:

add(new org.apache.ivy.plugins.resolver.FileSystemResolver()) {
name = 'localRepository'
changingPattern = '.*-SNAPSHOT'
checksums = "sha1,md5"
addArtifactPattern "${System.properties['user.home']}/.ivy2/local-repo/$artifactPattern"
addIvyPattern "${System.properties['user.home']}/.ivy2/local-repo/$ivyPattern"
}

even if I set
project.buildscript.configurations.all

{ resolutionStrategy.cacheChangingModulesFor 0, 'minutes' }

Gradle will never download a new jar with a -SNAPSHOT version. I have verified that if I use dynamic versions (i.e. latest.integration) and set the resolution strategy for dynamic versions it does work.

Is there some way to communicate to gradle that it should honor the changing pattern of the ivy resolvers with the new resolution code?

 Comments   
Comment by Gradle Forums [ 27/Feb/12 ]

Hi Sean,

Can you confirm that this worked for `1.0-milestone-7`?

Comment by Gradle Forums [ 27/Feb/12 ]

I know it is working with milestone-6 and before, I will try it with milestone-7 and report back.

Comment by Gradle Forums [ 27/Feb/12 ]

I have the same problem with milestone-7. It seems to handle dynamic versions just fine, but not changingVersions.

Comment by Gradle Forums [ 27/Feb/12 ]

Thanks for taking the time to find that out. That will make it easier to track down.

Comment by Detelin Yordanov [ 02/Mar/12 ]

A sample test case to verify whether changing module dependencies are refreshed by Gradle when there are new versions on the repository.
Requires:

  • Gradle 1.0-m8
  • Ivy http repository using Maven2 layout (see remoteRepo configuration in gradleUserHome/init.gradle)

The test case contains:

  • A org.foo:helloplugin module using a changing version (1.0-m1-SNAPSHOT but can be any)
  • A test module that defines a buildscript dependency to the helloplugin setting changing=true
  • A build script that builds and uploads the helloplugin, then runs the test module - this is done 3 times, each time checking whether the test module uses latest helloplugin

Please let me know if there are any misconfigurations or anything that needs to be changed, I also tried setting 

resolutionStrategy {
    cacheChangingModulesFor 0, 'seconds'
}

for the test module's buildscript configuration but it did not seem to help.

Regards,
Detelin

Comment by Benjamin Muschko [ 15/Nov/16 ]

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!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

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