From: Stefan B. <bo...@ap...> - 2015-02-21 16:35:24
|
On 2015-02-21, Joe Hayes wrote: > My name is Joe Hayes and I've just joined the list. welcome Joe. > Recently Stefan kindly accepted my pull request for creating and publishing > XmlUnit.NET NuGet packages. Note pack currently doesn't work on Linux, even after changing exec to invoke mono explicitly: [exec] Attempting to build package from 'xmlunit.nuspec'. [exec] File not found: 'build\net\bin\xmlunit-core.dll'. the file is there, using forward slashes, of course. I guess it is the file element in the nuspec file but didn't dare to change it to forward slashes. Looking through the nuget issue tracker "pack" seems to have other problems as well, so I'll have to resort to a Windows VM. As for the nuspec content, I'm not sure about the authors and owners elements, it seems authors is required. I'm sure I'd forget to update that line after accepting PRs. Can we use "XMLUnit contributors" as authors or is this frowned upon? > Some additional build/NuGet related TODOs (which I'm happy to work on): > - create an additional nuspec for the constraints assembly > - create a symbols package ( > https://docs.nuget.org/create/creating-and-publishing-a-symbol-package) does this include publishing the sources? > - adopt semantic version-ing for .NET build We are already publishing XMLUnit for Java SNAPSHOT builds (whenever I feel like it, not automatically). For nuget packages something like 2.0.0-alpha-01 would likely be a good initial version. > - .NET framework targeting are we missing anything? > - port build from NAnt to xBuild / MSBuild (a project file that can also > support IDEs) Your help is very much appreciated. Cheers Stefan |