-
Notifications
You must be signed in to change notification settings - Fork 526
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
Nuget feed v3 only #1143
Comments
Currently paket accepts only v2 urls and automatically tries to compute the You could look into this v3 url discovery (in NugetV3.fs) to make it work
|
(you are the first person that tells me there are nuget v3 servers that
|
There isnt one yet ;) |
I am working on a pr that will make Paket support a nuget feed that does not implement the v2 OData api. I think the source parameter needs to support explicitly setting the api version, ala Would you have any objections to that? |
For backwards compatibility any source that does not have a version explicitly set is assumed to be |
A lot of the tests specify a source with only a starting quote, not an ending quote: Does that functionality need to stay? Its making adding version to the parse a pain. |
I don't really understand why you need to change the parser. |
I am being an idiot. I was going to make it where you had to explicitly say that a source supported V3, no reason to do that though. 🙈 |
Implemented by #1205 |
Working on a private nuget feed implementing the v3 nuget 3 spec. If I set the feed in
paket.dependencies
toPaket uses the v2 methods to attempt to load the data. I would like to not have to implement the v2 api in my feed, its rather complicated for what I need to do. Any way to have Paket use the v3 api methods for a specific url? Maybe with an argument to source that hard codes the api version.
The text was updated successfully, but these errors were encountered: