Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-10062

NuGet server does not comply to the standard of defining dependencies

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.0.0, 2.13
    • Fix Version/s: None
    • Component/s: NuGet
    • Story Points:
      3

      Description

      With the release of NuGet version 3.4, we (the NuGet team) tightened the validation of dependencies. We found that NuGet used to take any invalid dependency and turn it into an empty one. That could lead into problems in package resolution or updates.

      It turns out that the nexus server is sending the string null to represent an empty dependency, which was not something the version parser could parse, and it turned into an error.

      We are going to allow it going forward (3.4.2+), but we recommend rectifying the string to be empty like all other servers do.

      Here is the bug in NuGet https://github.com/NuGet/Home/issues/2426
      Specifically this is the offending xml snippet:

      <d:Dependencies>XXXX.XX.XXX.Customer.Data:null|EntityFramework:6.1.3|YYYY.YY.YY.YYY.Security:3.7.0.15</d:Dependencies>

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            yishaigalatzer Yishai Galatzer
            Last Updated By:
            Damian Bradicich Damian Bradicich
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Date of First Response:

                tigCommentSecurity.panel-title