NuGet 3.0 support
[RTFACT-13090] Support for NuGet with SemVer 2.0 Created: 21/Dec/16 Updated: 17/May/18 Resolved: 09/May/18
|Project:||Artifactory Binary Repository|
|Reporter:||Jonathan Roquelaure||Assignee:||Maxim Yurkovsky|
With nuget client 3.5.0 the support of semver 2.0 start to be supported (in a limited way)
see doc here : https://github.com/NuGet/Home/wiki/SemVer-2.0.0-support
Semver 2.0 allows to have this format for nuget versioning : Major.Minor-beta.X (where X is a number).
Orange has sent me some packages to reproduce the error (so if you need them, just ask)
IMO more people will move to this semver 2.0 during Q1 2017 and we should be ready for it (specially when nuget.org will start to support it making our remote repo partially unusable on it)
|Comment by Stephen Drew [ 02/Oct/17 ]|
Is there any news on this? I see it's been open for almost a year. We are running into this issue in that Artifactory cannot proxy packages from nuget.org of the form "1.0.0-rc.1" which is valid Semver 2. Unfortunately, this renders Artifactory a bit useless for our purposes of caching all nuget packages.
|Comment by Stephen Drew [ 06/Nov/17 ]|
Further to this, we are looking at using GitVersion to version our packages and would like to use SemVer 2.0. So we are now in a situation where we cannot proxy SemVer 2 packages from nuget.org, and we cannot push our own packages to Artifactory if they are using SemVer 2.0. Given that this constitutes 95% of what we push, it means that unless this is on the roadmap for a fairly imminent release, we will have to start looking at other options
|Comment by Marty Lindsay [ 22/Nov/17 ]|
Any update on this one pls?
|Comment by Thomas Ulrich [ 24/Nov/17 ]|
JFrog, please move quickly on this. With more and more NuGet packages on nuget.org using SemVer 2.0, Artifactory is no longer a viable option as a nuget proxy. I can't help the feeling that amonst the more hip docker and npm features, decent support for other protocols such as NuGet and Maven is no longer on JFrog's agenda despite those protocols being widely used.
|Comment by Maxim Yurkovsky [ 06/May/18 ]|
This issue is contained in