Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ivy revision latest version Semver syntax is buggy. #7552

Closed
altrack opened this issue May 6, 2024 · 1 comment
Closed

Ivy revision latest version Semver syntax is buggy. #7552

altrack opened this issue May 6, 2024 · 1 comment
Labels

Comments

@altrack
Copy link

altrack commented May 6, 2024

steps

I'm running SBT version 1.9.9 (also happens in 1.9.8) on Mac M1 OS 14.4.1.
A dependency version defined with Ivy syntax to fetch latest minor version as following 1.+.
The resolver is an Artifactory server.
This definition works time to time.

problem

Issue: When I update the version of the dependency, it doesn't fetch the newest version.

Checking in the Artifcatory server and it has the new version folder and updated maven-metadata.xml.

I tried to kill + start SBT, reload the SBT, as well as run update, but nothing fixes the issue.

Checking the local cache at:
~/Library/Caches/Coursier/v1/https/artifactory.myserver.com/artifactory/sbt-main/com/company/mypackage_2.13
I see that maven-metadata.xml is not being updated to the latest version,
also the folder of the latest version doesn't exist.

This issue has been reproduced on multiple Mac computers.

Another check I did is setting the specific version of the latest dependency - works as expected.
After that changing back to 1.+ doesn't seem to fix the issue.

expectation

1.+ Ivy syntax in SBT fetches the latest version of the dependency.
This feature works time to time.

notes

Work-around delete the local cache folder of the package.

@altrack altrack added the Bug label May 6, 2024
@eed3si9n
Copy link
Member

This is because Coursier implements TTL. See https://get-coursier.io/docs/ttl please.

@eed3si9n eed3si9n closed this as not planned Won't fix, can't repro, duplicate, stale May 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants