Dotnet pack output moved after tooling upgrade

[SapientGuardian]

After upgrading from the older project.json based tooling to the VS2017 csproj tooling, the output of dotnet pack has moved to an unexpected location.

Sample repo: https://github.com/SapientGuardian/SapientGuardian.MarathonClient
Build with old tooling: https://ci.appveyor.com/project/SapientGuardian/sapientguardian-marathonclient/build/1.0.0-7
Build with new tooling: https://ci.appveyor.com/project/SapientGuardian/sapientguardian-marathonclient/build/1.0.0-11

Steps to reproduce

Create a nuget package from the root of a repository, with the library source in a subfolder, specifying an output which is a relative path from the root of the repository, not in the source folder.

dotnet pack .\src\SapientGuardian.MarathonClient -o .\artifacts\SapientGuardian.MarathonClient -c Release

Expected behavior

Output path is calculated from the root of the repository, where the dotnet pack command was run.

Producing nuget package "SapientGuardian.MarathonClient.0.1.1" for SapientGuardian.MarathonClient
SapientGuardian.MarathonClient -> C:\Repos\SapientGuardian.MarathonClient\artifacts\SapientGuardian.MarathonClient\SapientGuardian.MarathonClient.0.1.1.nupkg

Actual behavior

Output path is calculated from the project source directory.

Successfully created package 'C:\Repos\SapientGuardian.MarathonClient\src\SapientGuardian.MarathonClient\artifacts\SapientGuardian.MarathonClient\SapientGuardian.MarathonClient.0.1.1.nupkg'.

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.0)

Product Information:
Version: 1.0.0
Commit SHA-1 hash: e53429f

Runtime Environment:
OS Name: Windows
OS Version: 10.0.14393
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\1.0.0

[livarcocc]

Yes, this is a known issue and we are discussing taking this fix for 2.0.

[livarcocc]

We will track it at https://github.com/dotnet/cli/issues/4765.