Closed munkyjunky closed 7 years ago
nugets_pack
has drifted away from being able to use it correctly; hence the suggestion to create a unit/integration test for it, like already exist for ordinary fsproj/csproj files in the unit tests for this repositoryI've tried several ways of adding a name field, but can't see anything in the nuspec docs on how to do this. Is there anything I can change in my Rakefile or nuspec to get this working?
I'm not a ruby developer so there's not much I can do in the way of contributing tests to help get this issue sorted.
My recommendation then is that you override the keys in your csproj file <Id>...</Id>
. Other than that, if you're using a nuspec file you might as well just do:
task :nugets_pack do
system 'packages/Nuget.CommandLine/lib/NuGet.exe', %W|pack src/MyProject.nuspec|, clr_command: true
end
and be done with it. :)
Closing because of lack of reply.
I'm trying to get albacore working on my Windows machine and am having issues with nugets_pack. I've based my rakefile off that generated by
albacore init
.Rakefile
Nuspec (in
src/
folder in my project, named build.nuspec)When running
bundle exec rake --trace
I get the following outputI'm not sure if the issue is with the
fatal: ..: '..' is outside repository
log, or theinner_text
causing the problems. Checking in the file mentioned in the logs (project.rb:89
) it looks like albacore is trying to getProject.PropertyGroup.Platform
from my nuspec, however that property is a csproj property - not a nuget property.Using ruby 2.2.4, albacore 2.5.6