Artifactory URLs are also reachable via jfrog.io
See original GitHub issueDescription
The pull request #2073 fixed the resolution of artifactory hosted nuget packages. Artifactory changed for hosted enterprise licenses the base url. The packages are reachable also via jfrog.io
. The fact that one is also able to define custom host url’s makes the fix in #2073 rather questionable.
Repro steps
Create a new empty project
- create
paket.dependencies
file - add a
jfrog.io
source - add a dependency with a loose version constraint for it’s dependencies
Expected behavior
Paket resolved all dependencies to max
version
Actual behavior
Paket used the min
version
Known workarounds
Use artifactoryonline.com
URL’s instead
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
HTTP Settings
When using Artifactory as an self-hosted private Docker registry, the Docker client can access Artifactory through a reverse proxy or directly through ......
Read more >Transfer Artifactory Configuration and Files to JFrog Cloud
Download data-transfer.jar from https://releases.jfrog.io/artifactory/jfrog- ... You can then rerun the command to ensure that the URLs are accessible.
Read more >Deprecation of artifactoryonline.com domain
By June 30, 2017, JFrog Artifactory SaaS will use a new domain: jfrog.io, and the artifactoryonline.com domain will be deprecated.
Read more >Conan Repositories
A Remote Repository defined in Artifactory serves as a caching proxy for a registry managed at a remote URL such as https://center.conan.io, or...
Read more >Repository Management
Artifacts in a local repository can be accessed directly using the following URL: http://<host>:<port>/artifactory/<local-repository-name>/<artifact-path>.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Larusso please also keep reporting the issue to jfrog. If more customers complain about this bug (which #2073 is just working around as good as possible) maybe they’ll finally fix their broken feed paging implementation sometime…
I.e. the problem is that due the paging being broken, no more than ~80 versions can ever be found. The workaround in #2073 just makes sure that these are at least the newest ones, instead of the oldest ones.
Yes. For regression tests we’ll first need #2554 / #2511 though.