Skip to content

Update symbol package format and add Sourcelink #2019

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

Merged

Conversation

fredericDelaporte
Copy link
Member

NHibernate goes on building symbol.nupkg since v5.0 although they are no more consumable with library built from Sdk projects (new .csproj format).

We should switch to building snupkg, and to ease furthermore debugging, add SourceLink as requested by #1971.

Fixes #1971.
Replaces #2018.

Copy link
Member

@hazzik hazzik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@fredericDelaporte fredericDelaporte merged commit db0f002 into nhibernate:master Feb 26, 2019
@fredericDelaporte fredericDelaporte deleted the NugetSymbolSourceLink branch February 26, 2019 22:06
@@ -319,23 +319,12 @@
<in>
<items>
<include name="${nuget.nupackages.dir}/*.nupkg"/>
<exclude name="${nuget.nupackages.dir}/*.symbols.nupkg"/>
</items>
</in>
<do>
<echo message="nuget push -source https://nuget.org/ ${path::get-file-name(filename)} ${environment::newline()}" file="${nuget.nupackages.pushbatfile}" append="true"/>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This url is not correct for pushing snupkg. They are ignored on it, even when explicitly pushing them.
I am going to PR the required url for pushing snupkg along with the regular package.
Seen after publishing NHibernate.Caches 5.6, done nhibernate/NHibernate-Caches#74 for fixing it there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants