[GRADLE-3350] Dependencies with version of 'SNAPSHOT' should be treated as changing Created: 21/Oct/15  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Mark Vieira (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0


This issue was reported on the forums: https://discuss.gradle.org/t/snapshot-dependencies-are-not-detected-without-number/12254

Essentially, Maven seems to consider a version of "SNAPSHOT" (no prefix) the same as any other snapshot version (ex. 1.2.0-SNAPSHOT) when deploying to a repository. That is, the artifacts are deployed with a timestamp. Gradle cannot resolve such artifacts since it assumes no timestamp will be present in the URI. Setting changing = true is insufficient in this case.

Comment by Mark Vieira (Inactive) [ 21/Oct/15 ]

I'm not sure if this is the intended behavior by Maven or just an implementation detail. I can find no such documentation to indicate that a version of "SNAPSHOT" is valid. In fact, I've found some code which seems to imply this is not a valid version number:


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