[GRADLE-2640] Misleading log message when reusing cached resource Created: 19/Jan/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Daz DeBoer Assignee: Unassigned
Resolution: Won't Fix Votes: 0


When using --refresh-dependencies, if the SHA1 key or publish timestamp indicates that the locally cached resource is up-to-date, the following log messages are emitted:

19:46:34.028 [INFO] [org.gradle.api.internal.externalresource.transfer.DefaultCacheAwareExternalResourceAccessor] Cached resource is up-to-date (lastModified: Tue Sep 18 22:00:53 CEST 2012). [HTTP: http://repo1.maven.org/maven2/org/jruby/jruby-complete/1.6.8/jruby-complete-1.6.8.pom]
19:46:34.035 [DEBUG] [org.gradle.api.internal.artifacts.repositories.resolver.ExternalResourceResolver] Downloading http://repo1.maven.org/maven2/org/jruby/jruby-complete/1.6.8/jruby-complete-1.6.8.pom to /private/var/folders/7r/lwvxzqm10l716wzmh50_9_gm0000h2/T/gradle_download6989504506539141847bin

The second message is misleading, since Gradle is NOT downloading from the URL specified.

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:27:25 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.